All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Damato <joe@dama.to>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	florian.fainelli@broadcom.com, jonas.gorski@gmail.com,
	andrew@lunn.ch, olteanv@gmail.com, leitao@debian.org,
	yinjun.zhang@corigine.com, louis.peens@corigine.com,
	oss-drivers@corigine.com
Subject: Re: [PATCH net 3/5] eth: nfp: drop the replaced rule from the list when reprogramming fails
Date: Thu, 3 Sep 2026 13:32:31 -0700	[thread overview]
Message-ID: <apnZX0ITjgH6R8M4@devvm20253.cco0.facebook.com> (raw)
In-Reply-To: <20260903032611.3000029-4-kuba@kernel.org>

On Wed, Sep 02, 2026 at 08:26:09PM -0700, Jakub Kicinski wrote:
> nfp_net_fs_add() replaces an existing rule by deleting it from the
> hardware, decrementing nn->fs.count and programming the new one.  If
> nfp_net_fs_add_hw() fails the old entry stays on nn->fs.list - only the
> success path reaches list_replace() - so the list is one longer than
> nn->fs.count, and it advertises a rule whose hardware entry has already
> been torn down.
> 
> nn->fs.count is what ETHTOOL_GRXCLSRLCNT reports, so userspace then sizes
> its buffer one entry short of what the GRXCLSRLALL walk wants to write.
> That used to overwrite one u32 past the allocation; since the walk is
> bounded it is a permanent -EMSGSIZE instead, as nothing ever resyncs the
> counter.
> 
> Fixes: 9eb03bb1c035 ("nfp: add ethtool flow steering callbacks")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: leitao@debian.org
> CC: yinjun.zhang@corigine.com
> CC: louis.peens@corigine.com
> CC: oss-drivers@corigine.com
> ---
>  drivers/net/ethernet/netronome/nfp/nfp_net_ethtool.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)

Reviewed-by: Joe Damato <joe@dama.to>

  reply	other threads:[~2026-09-03 20:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  3:26 [PATCH net 0/5] eth: fix bugs in ntuple filter reporting Jakub Kicinski
2026-09-03  3:26 ` [PATCH net 1/5] net: dsa: bcm_sf2: bound the CFP rule dump by the caller's buffer size Jakub Kicinski
2026-09-03  8:30   ` Jonas Gorski
2026-09-03 15:24   ` Florian Fainelli
2026-09-03 20:12   ` Joe Damato
2026-09-03  3:26 ` [PATCH net 2/5] eth: nfp: bound the ntuple " Jakub Kicinski
2026-09-03 20:14   ` Joe Damato
2026-09-03  3:26 ` [PATCH net 3/5] eth: nfp: drop the replaced rule from the list when reprogramming fails Jakub Kicinski
2026-09-03 20:32   ` Joe Damato [this message]
2026-09-03  3:26 ` [PATCH net 4/5] net: dsa: mv88e6xxx: bound the policy rule dump by the caller's buffer size Jakub Kicinski
2026-09-03 20:20   ` Joe Damato
2026-09-03  3:26 ` [PATCH net 5/5] ethtool: document that GRXCLSRLALL rule_cnt is a caller-provided limit Jakub Kicinski
2026-09-03 20:16   ` Joe Damato
2026-09-04 22:30 ` [PATCH net 0/5] eth: fix bugs in ntuple filter reporting patchwork-bot+netdevbpf

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=apnZX0ITjgH6R8M4@devvm20253.cco0.facebook.com \
    --to=joe@dama.to \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=horms@kernel.org \
    --cc=jonas.gorski@gmail.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=louis.peens@corigine.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=oss-drivers@corigine.com \
    --cc=pabeni@redhat.com \
    --cc=yinjun.zhang@corigine.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.