[dpdk-stable] [PATCH v5] net/i40e: fix disabling promiscuous mode

Xu, Rosen rosen.xu at intel.com
Tue May 1 16:29:20 CEST 2018



> -----Original Message-----
> From: Luca Boccassi [mailto:bluca at debian.org]
> Sent: Tuesday, May 01, 2018 21:52
> To: Xu, Rosen <rosen.xu at intel.com>
> Cc: stable at dpdk.org
> Subject: Re: [dpdk-stable] [PATCH v5] net/i40e: fix disabling promiscuous
> mode
> 
> On Tue, 2018-05-01 at 13:27 +0000, Xu, Rosen wrote:
> > > -----Original Message-----
> > > From: Luca Boccassi [mailto:bluca at debian.org]
> > > Sent: Monday, April 30, 2018 21:43
> > > To: Xu, Rosen <rosen.xu at intel.com>
> > > Cc: stable at dpdk.org
> > > Subject: Re: [dpdk-stable] [PATCH v5] net/i40e: fix disabling
> > > promiscuous mode
> > >
> > > On Sat, 2018-04-28 at 19:37 +0800, Rosen Xu wrote:
> > > > v5 updates:
> > > > ===========
> > > >  - Modificate some comments for this patch
> > > >
> > > > v4 updates:
> > > > ===========
> > > >  - Add some comments for this patch
> > > >
> > > > v3 updates:
> > > > ===========
> > > >  - Move modification from device close to device disable
> > > >  - i40evf_reset_vf() will cause kernel driver enable all vlan
> > > > promiscuous,
> > > >    so unicast/multicast promiscuous disable should set before
> > > > reset.
> > > >
> > > > v2 updates:
> > > > ===========
> > > >  - Add more comments
> > > >
> > > > In scenario of Kernel Driver runs on PF and PMD runs on VF, PMD
> > > > exit doesn't disable promiscuous mode, this will cause vlan filter
> > > > set by Kernel Driver will not take effect.
> > > >
> > > > This patch will fix it, add promiscuous disable at device disable.
> > > >
> > > > Fixes: 4861cde46116 ("i40e: new poll mode driver")
> > > > Cc: stable at dpdk.org
> > > >
> > > > Signed-off-by: Rosen Xu <rosen.xu at intel.com>
> > > > Acked-by: Qi Zhang <qi.z.zhang at intel.com>
> > >
> > > Has this or a version of this fix been committed to mainline?
> >
> > I have submit the patch, the action of merging this patch is belongs
> > to maintainer.
> > Do you think so?
> 
> Yes - the reason I ask is because the process we follow for the stable releases
> is to tag commits that are backported with the commit ID of the patch that
> was merged into dpdk/master, for tracking.
> And also, for patches that to into dpdk/master, we wait to merge until the
> version to dpdk/master is merged first.

+Maintainers

> --
> Kind regards,
> Luca Boccassi


More information about the stable mailing list