From: patchwork-bot+netdevbpf@kernel.org
To: luoxuanqiang <xuanqiang.luo@linux.dev>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, idosch@nvidia.com, daniel@iogearbox.net,
ast@kernel.org, martin.lau@kernel.org, posk@google.com,
luoxuanqiang@kylinos.cn, stable@vger.kernel.org
Subject: Re: [PATCH net v1] bpf: lwt: Fix dst reference leak on reroute failure
Date: Tue, 28 Jul 2026 11:30:05 +0000 [thread overview]
Message-ID: <178523820589.1686123.3080651446763119610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260723060445.21926-1-xuanqiang.luo@linux.dev>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 23 Jul 2026 14:04:45 +0800 you wrote:
> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>
> bpf_lwt_xmit_reroute() obtains a referenced dst from the route
> lookup. When skb_cow_head() fails before that dst is installed on the
> skb, the error path only frees the skb. The skb still owns its previous
> dst, so the newly looked up dst reference is leaked.
>
> [...]
Here is the summary with links:
- [net,v1] bpf: lwt: Fix dst reference leak on reroute failure
https://git.kernel.org/netdev/net/c/88c17de85ddb
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-07-28 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 6:04 [PATCH net v1] bpf: lwt: Fix dst reference leak on reroute failure xuanqiang.luo
2026-07-24 6:06 ` sashiko-bot
2026-07-28 11:30 ` 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=178523820589.1686123.3080651446763119610.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@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=luoxuanqiang@kylinos.cn \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=posk@google.com \
--cc=stable@vger.kernel.org \
--cc=xuanqiang.luo@linux.dev \
/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