From: patchwork-bot+netdevbpf@kernel.org
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: theo.lebrun@bootlin.com, conor.dooley@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
claudiu.beznea@tuxon.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: macb: fix software FCS handling of shared and requeued skbs
Date: Thu, 08 Oct 2026 18:50:11 +0000 [thread overview]
Message-ID: <179148541151.391001.6091516917596389045.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261006-nb-macb-shared-skb-net-v1-0-a80641479041@tipi-net.de>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 06 Oct 2026 07:41:31 +0200 you wrote:
> While testing the genet MTU series I used a Raspberry Pi CM5 (RP1 GEM)
> as pktgen source for the CM4. With clone_skb the CM5 rebooted after a
> few seconds. Further investigation showed that macb_pad_and_fcs()
> appends the FCS in place, so the shared skb grows with every transmit
> until BQL completes more than was queued and dql_completed() hits its
> BUG_ON.
>
> [...]
Here is the summary with links:
- [net,1/2] net: macb: check TX ring before modifying skb
https://git.kernel.org/netdev/net/c/6b48ed85ae0c
- [net,2/2] net: macb: copy shared skbs before appending the FCS
https://git.kernel.org/netdev/net/c/9151d6c42799
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-08 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 5:41 [PATCH net 0/2] net: macb: fix software FCS handling of shared and requeued skbs Nicolai Buchwitz
2026-10-06 5:41 ` [PATCH net 1/2] net: macb: check TX ring before modifying skb Nicolai Buchwitz
2026-10-06 5:41 ` [PATCH net 2/2] net: macb: copy shared skbs before appending the FCS Nicolai Buchwitz
2026-10-08 18:50 ` 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=179148541151.391001.6091516917596389045.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=theo.lebrun@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox