All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
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,
	alexanderduyck@fb.com, mohsin.bashr@gmail.com,
	vadim.fedorenko@linux.dev
Subject: Re: [PATCH net] eth: fbnic: unlink NAPIs from queues on error to open
Date: Tue, 05 Aug 2025 00:30:25 +0000	[thread overview]
Message-ID: <175435382599.1400451.2596068908242248533.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250728163129.117360-1-kuba@kernel.org>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 28 Jul 2025 09:31:29 -0700 you wrote:
> CI hit a UaF in fbnic in the AF_XDP portion of the queues.py test.
> The UaF is in the __sk_mark_napi_id_once() call in xsk_bind(),
> NAPI has been freed. Looks like the device failed to open earlier,
> and we lack clearing the NAPI pointer from the queue.
> 
> Fixes: 557d02238e05 ("eth: fbnic: centralize the queue count and NAPI<>queue setting")
> Reviewed-by: Alexander Duyck <alexanderduyck@fb.com>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> 
> [...]

Here is the summary with links:
  - [net] eth: fbnic: unlink NAPIs from queues on error to open
    https://git.kernel.org/netdev/net/c/4b31bcb025cb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-08-05  0:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 16:31 [PATCH net] eth: fbnic: unlink NAPIs from queues on error to open Jakub Kicinski
2025-07-29 11:15 ` Simon Horman
2025-08-05  0:30 ` patchwork-bot+netdevbpf [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=175435382599.1400451.2596068908242248533.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexanderduyck@fb.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=mohsin.bashr@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vadim.fedorenko@linux.dev \
    /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.