patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <>
To: Ivan Malov <>,
Cc:, Andy Moreton <>,
	Andrew Rybchenko <>
Subject: Re: [dpdk-stable] [PATCH 1/3] common/sfc_efx/base: fix MAE match spec validation helper
Date: Mon, 18 Jan 2021 09:05:16 +0000
Message-ID: <> (raw)
In-Reply-To: <>

On 1/6/2021 10:05 AM, Ivan Malov wrote:
> A particular FW version is aware of some set of match fields.
> Depending on FW configuration and match specification type, a
> known field may not necessarily be allowed to have a non-zero
> mask. FW communicates such restrictions via field capabilities
> MCDI. Newer FW may be aware of more fields. For such fields,
> older FW simply does not report any capabilities.
> A situation may occur when libefx is aware of a match field
> which the FW is unaware of (eg., older FW), that is, FW does
> not report capability status for this field. In this case,
> libefx must consider such field as unsupported and demand
> all-zeros mask for it when validating match specifications.
> Currently, the helper in question simply exits and reports
> that the specification is valid when it encounters a field
> with no capability status available. This is clearly wrong.
> Introduce the missing check to fix the problem.
> Fixes: 34285fd0891d ("common/sfc_efx/base: add match spec validate API")
> Cc:
> Reviewed-by: Andy Moreton <>
> Reviewed-by: Andrew Rybchenko <>
> Signed-off-by: Ivan Malov <>

Series applied to dpdk-next-net/main, thanks.

      parent reply	other threads:[~2021-01-18  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 10:05 Ivan Malov
2021-01-06 10:06 ` [dpdk-stable] [PATCH 2/3] common/sfc_efx/base: fix MAE match spec class comparison API Ivan Malov
2021-01-06 10:06 ` [dpdk-stable] [PATCH 3/3] common/sfc_efx/base: enhance field ID check in field set API Ivan Malov
2021-01-18  9:05 ` Ferruh Yigit [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ \
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone