From: patchwork-bot+netdevbpf@kernel.org
To: Josef Bacik <josef@toxicpanda.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/8] net: skbuff: replace most BUG_ON()s with error returns
Date: Fri, 16 Oct 2026 01:00:10 +0000 [thread overview]
Message-ID: <179211241001.4182913.5200516611523638723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007-b4-skbuff-bug-on-v2-0-b9a5f732895b@toxicpanda.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 07 Oct 2026 17:35:59 +0000 you wrote:
> v1: https://lore.kernel.org/all/20261006-b4-skbuff-bug-on-v1-0-1b4434c5357c@toxicpanda.com/
>
> v1->v2:
> - Use DEBUG_NET_WARN_ON_ONCE() instead of WARN_ON_ONCE(), so
> panic_on_warn systems take the error path instead of panicking
> (Willem, Fernando).
> - Split out the skb_copy_and_csum_bits() unreadable-frags fix and sent
> it to net on its own with Cc: stable (Willem):
> https://lore.kernel.org/all/20261007-b4-skb-copy-csum-stale-bytes-v1-1-adbbde033fb3@toxicpanda.com/
> - Rebased onto current net-next.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/8] net: skbuff: don't BUG() on bad arguments to pskb_expand_head()
https://git.kernel.org/netdev/net-next/c/c7d8bc3dd511
- [net-next,v2,2/8] net: skbuff: don't BUG() on a bad frag_list layout in skb_segment()
https://git.kernel.org/netdev/net-next/c/7b32bee7db82
- [net-next,v2,3/8] net: skbuff: don't BUG() when skb_copy_bits() fails in copy helpers
https://git.kernel.org/netdev/net-next/c/279877d86c82
- [net-next,v2,4/8] net: skbuff: don't BUG() on leftover length in skb_checksum() and friends
https://git.kernel.org/netdev/net-next/c/20ddd0fd2fcd
- [net-next,v2,5/8] net: skbuff: don't BUG() on a bad csum_start in skb_copy_and_csum_dev()
https://git.kernel.org/netdev/net-next/c/56453199d28f
- [net-next,v2,6/8] net: skbuff: don't BUG() on leftover length in skb_copy_and_csum_bits()
https://git.kernel.org/netdev/net-next/c/417261779eab
- [net-next,v2,7/8] net: skbuff: don't BUG() on a missing head_frag in skb_zerocopy()
https://git.kernel.org/netdev/net-next/c/433380f5ab8f
- [net-next,v2,8/8] net: skbuff: remove the BUG_ON()s from skb_shift()
https://git.kernel.org/netdev/net-next/c/e6974aad4bd7
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-16 1:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 17:35 Josef Bacik
2026-10-07 17:36 ` [PATCH net-next v2 1/8] net: skbuff: don't BUG() on bad arguments to pskb_expand_head() Josef Bacik
2026-10-07 17:36 ` [PATCH net-next v2 2/8] net: skbuff: don't BUG() on a bad frag_list layout in skb_segment() Josef Bacik
2026-10-11 17:00 ` netdev-bot+sashiko
2026-10-07 17:36 ` [PATCH net-next v2 3/8] net: skbuff: don't BUG() when skb_copy_bits() fails in copy helpers Josef Bacik
2026-10-11 17:00 ` netdev-bot+sashiko
2026-10-07 17:36 ` [PATCH net-next v2 4/8] net: skbuff: don't BUG() on leftover length in skb_checksum() and friends Josef Bacik
2026-10-11 17:00 ` netdev-bot+sashiko
2026-10-07 17:36 ` [PATCH net-next v2 5/8] net: skbuff: don't BUG() on a bad csum_start in skb_copy_and_csum_dev() Josef Bacik
2026-10-11 17:00 ` netdev-bot+sashiko
2026-10-07 17:36 ` [PATCH net-next v2 6/8] net: skbuff: don't BUG() on leftover length in skb_copy_and_csum_bits() Josef Bacik
2026-10-11 17:00 ` netdev-bot+sashiko
2026-10-07 17:36 ` [PATCH net-next v2 7/8] net: skbuff: don't BUG() on a missing head_frag in skb_zerocopy() Josef Bacik
2026-10-11 17:00 ` netdev-bot+sashiko
2026-10-07 17:36 ` [PATCH net-next v2 8/8] net: skbuff: remove the BUG_ON()s from skb_shift() Josef Bacik
2026-10-16 1:00 ` 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=179211241001.4182913.5200516611523638723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®