From: patchwork-bot+netdevbpf@kernel.org
To: Matt Fleming <matt@readmodwrite.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, hawk@kernel.org,
john.fastabend@gmail.com, sdf@fomichev.me, lorenzo@kernel.org,
toke@toke.dk, bpf@vger.kernel.org, netdev@vger.kernel.org,
stable@vger.kernel.org, kernel-team@cloudflare.com,
mfleming@cloudflare.com
Subject: Re: [PATCH bpf v2] veth: convert frag_list skbs before running XDP
Date: Tue, 21 Jul 2026 16:50:05 +0000 [thread overview]
Message-ID: <178465260565.839953.7972365481675163007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260720140545.461747-1-matt@readmodwrite.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Mon, 20 Jul 2026 15:05:45 +0100 you wrote:
> From: Matt Fleming <mfleming@cloudflare.com>
>
> A frag_list skb can reach veth with data_len set but nr_frags zero.
> veth_convert_skb_to_xdp_buff() only converts skbs that are shared,
> locked, have frags[], or do not have enough headroom. It later uses
> skb_is_nonlinear() to decide whether to set XDP_FLAGS_HAS_FRAGS and
> xdp_frags_size.
>
> [...]
Here is the summary with links:
- [bpf,v2] veth: convert frag_list skbs before running XDP
https://git.kernel.org/bpf/bpf/c/c3e0e81eec96
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-07-21 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:05 [PATCH bpf v2] veth: convert frag_list skbs before running XDP Matt Fleming
2026-07-20 20:28 ` Toke Høiland-Jørgensen
2026-07-21 10:05 ` Lorenzo Bianconi
2026-07-21 16:50 ` patchwork-bot+netdevbpf [this message]
2026-07-21 21:14 ` Jakub Kicinski
2026-07-21 21:28 ` Kumar Kartikeya Dwivedi
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=178465260565.839953.7972365481675163007.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@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=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=matt@readmodwrite.com \
--cc=mfleming@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=stable@vger.kernel.org \
--cc=toke@toke.dk \
/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