From: patchwork-bot+netdevbpf@kernel.org
To: Yuqiang Sun <izaiahsun@gmail.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, ast@kernel.org, tgraf@suug.ch,
zirajs7@gmail.com, bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] bpf: lwt: Free the skb when bpf_xmit() fails to expand the headroom
Date: Mon, 02 Nov 2026 06:20:04 +0000 [thread overview]
Message-ID: <179360040431.3799098.11662321290376218283.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261101182343.17991-1-izaiahsun@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 2 Nov 2026 02:23:43 +0800 you wrote:
> When an LWT xmit program returns BPF_OK, bpf_xmit() makes sure that
> the skb still has room for the link layer header. If
> pskb_expand_head() fails there, bpf_xmit() returns -ENOMEM without
> freeing the skb. Its callers, lwtunnel_xmit() and then
> ip_finish_output2() or ip6_finish_output2(), take any return value
> other than LWTUNNEL_XMIT_CONTINUE to mean that the skb has been
> consumed, so nothing frees it.
>
> [...]
Here is the summary with links:
- [net] bpf: lwt: Free the skb when bpf_xmit() fails to expand the headroom
https://git.kernel.org/bpf/bpf/c/5e96760b25fd
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-11-02 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 18:23 Yuqiang Sun
2026-11-02 6: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=179360040431.3799098.11662321290376218283.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=izaiahsun@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=zirajs7@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
all inboxes | Powered by JetHome®