From: patchwork-bot+netdevbpf@kernel.org
To: Jesper Dangaard Brouer <hawk@kernel.org>
Cc: netdev@vger.kernel.org, bigeasy@linutronix.de,
bpf@vger.kernel.org, eric.dumazet@gmail.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com,
makita.toshiaki@lab.ntt.co.jp, toshiaki.makita1@gmail.com,
kernel-team@cloudflare.com, mfleming@cloudflare.com,
maciej.fijalkowski@intel.com, dtatulea@nvidia.com,
edumazet@google.com, sdf@fomichev.me, andrew+netdev@lunn.ch,
john.fastabend@gmail.com, ast@kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH net V1] veth: reduce XDP no_direct return section to fix race
Date: Fri, 21 Nov 2025 02:50:06 +0000 [thread overview]
Message-ID: <176369340676.1872917.10033820911607185315.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <176356963888.337072.4805242001928705046.stgit@firesoul>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Nov 2025 17:28:36 +0100 you wrote:
> As explain in commit fa349e396e48 ("veth: Fix race with AF_XDP exposing
> old or uninitialized descriptors") for veth there is a chance after
> napi_complete_done() that another CPU can manage start another NAPI
> instance running veth_pool(). For NAPI this is correctly handled as the
> napi_schedule_prep() check will prevent multiple instances from getting
> scheduled, but for the remaining code in veth_pool() this can run
> concurrent with the newly started NAPI instance.
>
> [...]
Here is the summary with links:
- [net,V1] veth: reduce XDP no_direct return section to fix race
https://git.kernel.org/netdev/net/c/a14602fcae17
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-21 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 16:28 [PATCH net V1] veth: reduce XDP no_direct return section to fix race Jesper Dangaard Brouer
2025-11-21 2:50 ` 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=176369340676.1872917.10033820911607185315.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=mfleming@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=toshiaki.makita1@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox