From: patchwork-bot+netdevbpf@kernel.org
To: Qihang <q.h.hack.winter@gmail.com>
Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
willemb@google.com, daniel.zahka@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v6 0/3] net: fix hard_header_len races in packet send paths
Date: Thu, 06 Aug 2026 16:50:22 +0000 [thread overview]
Message-ID: <178603502213.1375455.2088843819224139687.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260805125729.19220-1-q.h.hack.winter@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 5 Aug 2026 20:57:26 +0800 you wrote:
> From: Qihang Tang <q.h.hack.winter@gmail.com>
>
> The packet socket TX paths read dev->hard_header_len independently for
> skb allocation and header construction. Concurrent netdevice
> reconfiguration (e.g. bonding device type changes) can change this value
> in between, leading to mismatched headroom and copy length, and in the
> SOCK_RAW case to out-of-bounds writes.
>
> [...]
Here is the summary with links:
- [net,v6,1/3] net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header
https://git.kernel.org/netdev/net/c/3b9a324e646d
- [net,v6,2/3] packet: use consistent hard_header_len in non-ring send paths
https://git.kernel.org/netdev/net/c/03390aa32e66
- [net,v6,3/3] packet: use consistent hard_header_len in TX_RING send path
https://git.kernel.org/netdev/net/c/21b5953e7494
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-08-06 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 12:57 [PATCH net v6 0/3] net: fix hard_header_len races in packet send paths Qihang
2026-08-05 12:57 ` [PATCH net v6 1/3] net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header Qihang
2026-08-06 3:07 ` Willem de Bruijn
2026-08-05 12:57 ` [PATCH net v6 2/3] packet: use consistent hard_header_len in non-ring send paths Qihang
2026-08-05 12:57 ` [PATCH net v6 3/3] packet: use consistent hard_header_len in TX_RING send path Qihang
2026-08-06 16:50 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-30 8:29 [PATCH net v5 0/2] packet: use consistent hard_header_len in send paths Qihang
2026-08-04 9:00 ` [PATCH net v6 0/3] net: fix hard_header_len races in packet " Qihang
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=178603502213.1375455.2088843819224139687.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=q.h.hack.winter@gmail.com \
--cc=stable@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.