From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
ndaugoing@gmail.com, stable@vger.kernel.org,
socketcan@hartkopp.net, quchaosheng000406@163.com,
shaunakkdatar@gmail.com
Subject: Re: [PATCH net 1/3] can: dev: init_can_skb(): restore skb header initialization
Date: Wed, 07 Oct 2026 01:20:05 +0000 [thread overview]
Message-ID: <179133600528.2856050.12084143172913855186.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001151905.1556270-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Thu, 1 Oct 2026 17:14:23 +0200 you wrote:
> From: zjamg <ndaugoing@gmail.com>
>
> Commit 9f10374bb024 ("can: remove private CAN skb headroom infrastructure")
> removed the skb_reset_mac_header()/skb_reset_network_header()/
> skb_reset_transport_header() calls from init_can_skb(). As a result, RX
> skbs from alloc_can_skb() and friends again carry mac_header = 0xFFFF.
> When such an skb reaches packet_rcv_spkt() (SOCK_PACKET), the push length
> calculation overflows and triggers skb_under_panic -> kernel BUG -> full
> machine panic.
>
> [...]
Here is the summary with links:
- [net,1/3] can: dev: init_can_skb(): restore skb header initialization
https://git.kernel.org/netdev/net/c/0a04c0cb8606
- [net,2/3] can: fix unique skb identifier regression under RPS
https://git.kernel.org/netdev/net/c/7093c3b8314a
- [net,3/3] usb: f81604: fix struct f81604_int_data size mismatch
https://git.kernel.org/netdev/net/c/7f85d1170575
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-10-07 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 15:14 [PATCH net 0/3] pull-request: can 2026-10-01 Marc Kleine-Budde
2026-10-01 15:14 ` [PATCH net 1/3] can: dev: init_can_skb(): restore skb header initialization Marc Kleine-Budde
2026-10-07 1:20 ` patchwork-bot+netdevbpf [this message]
2026-10-01 15:14 ` [PATCH net 2/3] can: fix unique skb identifier regression under RPS Marc Kleine-Budde
2026-10-01 15:14 ` [PATCH net 3/3] usb: f81604: fix struct f81604_int_data size mismatch Marc Kleine-Budde
2026-10-05 9:30 ` Marc Kleine-Budde
2026-10-02 7:55 ` [PATCH net 0/3] pull-request: can 2026-10-01 Paolo Abeni
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=179133600528.2856050.12084143172913855186.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=ndaugoing@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=quchaosheng000406@163.com \
--cc=shaunakkdatar@gmail.com \
--cc=socketcan@hartkopp.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