public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH] net/i40e: fix FDIR VLAN TCI partial mask validation
Date: Fri, 3 Apr 2026 14:56:20 +0100	[thread overview]
Message-ID: <ac_HBOeVnBKj0akg@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260323104345.1667974-1-ciara.loftus@intel.com>

On Mon, Mar 23, 2026 at 10:43:45AM +0000, Ciara Loftus wrote:
> Currently, the i40e flow validation logic accepts some partial VLAN TCI
> masks alongside the full mask, and reports an error for any other value.
> This is broken in two ways.
> 
> First, the error case is not handled correctly. An error is recorded
> however execution continues as normal, and a filter is programmed using
> the invalid mask, silently producing wrong matching behaviour.
> 
> Second, the hardware always compares the full 16-bit TCI field with no
> per-bit masking. Partial masks are therefore not honoured and should not
> be accepted.
> 
> Fix this by accepting only either a wildcard or exact match mask and
> handle the invalid mask cases appropriately.
> 
> Bugzilla ID: 1340
> Fixes: 81aebb47d1 ("net/i40e: fix flow director for eth + VLAN pattern")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
>  drivers/net/intel/i40e/i40e_flow.c | 20 +++++++-------------
>  1 file changed, 7 insertions(+), 13 deletions(-)
> 
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied to dpdk-next-net-intel,

Thanks,
/Bruce

      reply	other threads:[~2026-04-03 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 10:43 [PATCH] net/i40e: fix FDIR VLAN TCI partial mask validation Ciara Loftus
2026-04-03 13:56 ` Bruce Richardson [this message]

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=ac_HBOeVnBKj0akg@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --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