From: patchwork-bot+netdevbpf@kernel.org
To: Qing Ming <a0yami@mailbox.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, kuniyu@google.com,
gnault@redhat.com, sd@queasysnail.net, dsahern@kernel.org,
rshearma@brocade.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] mpls: reload header after pskb_may_pull()
Date: Tue, 18 Aug 2026 09:20:05 +0000 [thread overview]
Message-ID: <178704480565.1975811.9540207161896507600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260814095404.7205-1-a0yami@mailbox.org>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 14 Aug 2026 17:54:04 +0800 you wrote:
> mpls_select_multipath() calls mpls_multipath_hash() to choose a nexthop
> when an MPLS route has multiple nexthops. While walking the MPLS label
> stack, the hash routine caches hdr for the current label. After finding
> the bottom-of-stack label, it calls pskb_may_pull() before reading the
> inner IP header.
>
> If an skb is constructed with the inner IP header in nonlinear data and
> insufficient tailroom in the linear head, pskb_may_pull() calls
> pskb_expand_head() to replace the skb head and free the old one. This
> leaves hdr pointing to freed memory. The IPv6 path can invalidate hdr
> again when it performs a second pull for the larger header.
>
> [...]
Here is the summary with links:
- [net] mpls: reload header after pskb_may_pull()
https://git.kernel.org/netdev/net/c/29e63b8d9fc1
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-18 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 9:54 [PATCH net] mpls: reload header after pskb_may_pull() Qing Ming
2026-08-18 7:55 ` Simon Horman
2026-08-18 9: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=178704480565.1975811.9540207161896507600.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a0yami@mailbox.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rshearma@brocade.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.kernel.org \
/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