From: Luca Boccassi <bluca@debian.org>
To: Andrew Rybchenko <arybchenko@solarflare.com>, arybchik@oktetlabs.ru
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/sfc: cut non VLAN ID bits from TCI
Date: Thu, 26 Jul 2018 10:46:54 +0100 [thread overview]
Message-ID: <1532598414.20916.22.camel@debian.org> (raw)
In-Reply-To: <4de7a434-ea9f-8f0c-fd11-6b3c6419ad7c@solarflare.com>
On Thu, 2018-07-26 at 12:42 +0300, Andrew Rybchenko wrote:
> On 23.07.2018 20:10, Luca Boccassi wrote:
> > On Wed, 2018-07-11 at 10:46 +0100, Andrew Rybchenko wrote:
> > > TCI may contain PCP or DEI bits. Matching of these bits is not
> > > supported, but the bits still may be set in specification value
> > > and
> > > not covered by mask. So, these bits should be ignored.
> > >
> > > Fixes: 894080975e1e ("net/sfc: support VLAN in flow API filters")
> > > Cc: stable@dpdk.org
> > >
> > > Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
> > > Reviewed-by: Roman Zhukov <roman.zhukov@oktetlabs.ru>
> > > ---
> > > drivers/net/sfc/sfc_flow.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/net/sfc/sfc_flow.c
> > > b/drivers/net/sfc/sfc_flow.c
> > > index 5613d59a9..18387415e 100644
> > > --- a/drivers/net/sfc/sfc_flow.c
> > > +++ b/drivers/net/sfc/sfc_flow.c
> > > @@ -371,7 +371,8 @@ sfc_flow_parse_vlan(const struct
> > > rte_flow_item
> > > *item,
> > > * the outer tag and the next matches the inner tag.
> > > */
> > > if (mask->tci == supp_mask.tci) {
> > > - vid = rte_bswap16(spec->tci);
> > > + /* Apply mask to keep VID only */
> > > + vid = rte_bswap16(spec->tci & mask->tci);
> > >
> > > if (!(efx_spec->efs_match_flags &
> > > EFX_FILTER_MATCH_OUTER_VID)) {
> >
> > Hi Andrew,
> >
> > For which stable release branch is this patch intended? Has it (or
> > an
> > equivalent) been merged into mainline?
>
> Hi Luka,
>
> Yes, the patch is applied in mainline [1].
>
> It would be good if it is applied to 17.11, 18.02 and 18.05 stable
> branches.
>
> [1]
> https://git.dpdk.org/dpdk/commit/?id=8028142107a858a146bfdbaa010b7e77
> ff987342
>
> Thanks,
> Andrew.
Ok, thanks, in the future please use --subject-prefix='PATCH xx.yy'
with git send-email to indicate the target branch(es)
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-07-26 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 9:46 Andrew Rybchenko
2018-07-23 17:10 ` Luca Boccassi
2018-07-26 9:42 ` Andrew Rybchenko
2018-07-26 9:46 ` Luca Boccassi [this message]
2018-07-26 9:50 ` Andrew Rybchenko
2018-07-26 9:52 ` Andrew Rybchenko
2018-07-26 10:03 ` Luca Boccassi
-- strict thread matches above, loose matches on Subject: below --
2018-06-29 15:23 Andrew Rybchenko
2018-07-04 17:43 ` Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1532598414.20916.22.camel@debian.org \
--to=bluca@debian.org \
--cc=arybchenko@solarflare.com \
--cc=arybchik@oktetlabs.ru \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).