From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, eric.dumazet@gmail.com,
mitch@sfgoth.com, 3chas3@gmail.com, qingfang.deng@linux.dev
Subject: Re: [PATCH v2 net] pppoatm: ensure a writable skb header and linear data
Date: Wed, 16 Sep 2026 00:10:06 +0000 [thread overview]
Message-ID: <178951740612.2328807.2734322587316636220.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260912233048.3977192-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 12 Sep 2026 23:30:48 +0000 you wrote:
> In pppoatm_send(), LLC encapsulation checks whether there is sufficient
> headroom for the 4-byte LLC header, but does not ensure that the skb header
> is writable.
>
> Normal transmit packets passing through ppp_start_xmit() have their header
> unshared via skb_cow_head(). However, packets can also reach pppoatm_send()
> via PPP channel bridging (PPPIOCBRIDGECHAN) without going through
> ppp_start_xmit().
>
> [...]
Here is the summary with links:
- [v2,net] pppoatm: ensure a writable skb header and linear data
https://git.kernel.org/netdev/net/c/ecc7253683a3
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-09-16 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 23:30 [PATCH v2 net] pppoatm: ensure a writable skb header and linear data Eric Dumazet
2026-09-13 23:32 ` netdev-bot+sashiko
2026-09-13 23:49 ` Eric Dumazet
2026-09-13 23:58 ` Eric Dumazet
2026-09-14 10:33 ` Simon Horman
2026-09-16 0:10 ` 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=178951740612.2328807.2734322587316636220.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=3chas3@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=mitch@sfgoth.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@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