From: patchwork-bot+netdevbpf@kernel.org
To: Chengfeng Ye <nicoyip.dev@gmail.com>
Cc: jchapman@katalix.com, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] l2tp: snapshot sequencing state when building transmit headers
Date: Tue, 20 Oct 2026 09:40:05 +0000 [thread overview]
Message-ID: <179248920528.3616761.4424083944726406723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013090500.1180376-1-nicoyip.dev@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 13 Oct 2026 17:05:00 +0800 you wrote:
> Updates to send_seq from netlink, PPP setsockopt and receive-side
> negotiation race with packet transmission. The header length is updated
> separately, while transmit reads both fields repeatedly without
> synchronization.
>
> For example, transmit can push a ten-byte L2TPv2 header, then a concurrent
> writer clears send_seq before the header builder reads it. The builder
> writes only six bytes, leaving four bytes of uninitialized skb headroom
> in the outgoing packet. The reverse mismatch overwrites the beginning of
> the payload. A later hdr_len read can also make the UDP length disagree
> with the skb length.
>
> [...]
Here is the summary with links:
- [net] l2tp: snapshot sequencing state when building transmit headers
https://git.kernel.org/netdev/net/c/d06ae66516e1
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-10-20 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:05 Chengfeng Ye
2026-10-20 9:40 ` 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=179248920528.3616761.4424083944726406723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicoyip.dev@gmail.com \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®