From: patchwork-bot+netdevbpf@kernel.org
To: Weiming Shi <bestswngs@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
kuba@kernel.org, hawk@kernel.org, john.fastabend@gmail.com,
sdf@fomichev.me, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, bjorn@kernel.org, xmei5@asu.edu,
stable@vger.kernel.org
Subject: Re: [PATCH net] xdp: fix zero-copy frame layout
Date: Sat, 22 Aug 2026 20:20:11 +0000 [thread overview]
Message-ID: <178743001114.1816901.15925905192026012486.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260818154516.793517-1-bestswngs@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Aug 2026 23:45:15 +0800 you wrote:
> xdp_convert_zc_to_xdp_frame() clones an XSK packet into an order-0 page
> and advertises PAGE_SIZE as its frame size. It allows the copied frame
> to occupy the page tail needed by skb_shared_info and records zero
> headroom even when metadata separates the frame header from packet data.
> An AF_XDP zero-copy packet redirected through cpumap can therefore make
> the skb overlap skb_shared_info or place it beyond the allocated page.
>
> [...]
Here is the summary with links:
- [net] xdp: fix zero-copy frame layout
https://git.kernel.org/netdev/net/c/71283aaa6c65
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-08-22 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 15:45 [PATCH net] xdp: fix zero-copy frame layout Weiming Shi
2026-08-19 15:49 ` sashiko-bot
2026-08-22 20:20 ` 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=178743001114.1816901.15925905192026012486.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bestswngs@gmail.com \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=stable@vger.kernel.org \
--cc=xmei5@asu.edu \
/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