From: patchwork-bot+netdevbpf@kernel.org
To: Nikhil P. Rao <nikhil.rao@amd.com>
Cc: netdev@vger.kernel.org, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, sdf@fomichev.me,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, kerneljasonxing@gmail.com
Subject: Re: [PATCH net v5 0/2] xsk: Fixes for AF_XDP fragment handling
Date: Sat, 28 Feb 2026 17:00:08 +0000 [thread overview]
Message-ID: <177229800880.3015444.1592823665460891413.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260225000456.107806-1-nikhil.rao@amd.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 25 Feb 2026 00:00:25 +0000 you wrote:
> This series fixes two issues in AF_XDP zero-copy fragment handling:
>
> Patch 1 fixes a buffer leak caused by incorrect list node handling after
> commit b692bf9a7543. The list_node field is now reused for both the xskb
> pool list and the buffer free list. Using list_del() instead of
> list_del_init() causes list_empty() checks in xp_free() to fail, preventing
> buffers from being added to the free list.
>
> [...]
Here is the summary with links:
- [net,v5,1/2] xsk: Fix fragment node deletion to prevent buffer leak
https://git.kernel.org/netdev/net/c/60abb0ac11dc
- [net,v5,2/2] xsk: Fix zero-copy AF_XDP fragment drop
https://git.kernel.org/netdev/net/c/f7387d6579d6
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:[~2026-02-28 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 0:00 [PATCH net v5 0/2] xsk: Fixes for AF_XDP fragment handling Nikhil P. Rao
2026-02-25 0:00 ` [PATCH net v5 1/2] xsk: Fix fragment node deletion to prevent buffer leak Nikhil P. Rao
2026-02-25 0:00 ` [PATCH net v5 2/2] xsk: Fix zero-copy AF_XDP fragment drop Nikhil P. Rao
2026-02-28 17:00 ` 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=177229800880.3015444.1592823665460891413.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nikhil.rao@amd.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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