From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] net: minor __alloc_skb() optimization
Date: Tue, 13 Jan 2026 18:30:08 -0800 [thread overview]
Message-ID: <20260113183008.15175891@kernel.org> (raw)
In-Reply-To: <CANn89iKDrx0DP56AynzMuKv4so7DFEFpFE2yHg6gCGugzd4ivQ@mail.gmail.com>
On Wed, 14 Jan 2026 02:54:10 +0100 Eric Dumazet wrote:
> We could keep it for a while, WDYT of
>
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index 77508cf7c41e829a11a988d8de3d2673ff1ff121..ccd287ff46e91c2548483c51fa32fc6167867940
> 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -458,7 +458,8 @@ static void __build_skb_around(struct sk_buff
> *skb, void *data,
> /* frag_size == 0 is considered deprecated now. Callers
> * using slab buffer should use slab_build_skb() instead.
> */
> - if (WARN_ONCE(size == 0, "Use slab_build_skb() instead"))
> + if (IS_ENABLED(CONFIG_DEBUG_NET) &&
> + WARN_ONCE(size == 0, "Use slab_build_skb() instead"))
> data = __slab_build_skb(data, &size);
Probably not worth it. People who use relevant HW + 3 year old kernels
(I just checked, we added the warning in Dec 2022) likely don't set
DEBUG_NET either. That said looks like the warning landed in 6.2,
narrowly missing the v6.1 LTS. I suppose v6.1 may still be used by some
"enterprise-ish" distroes. I guess we should wait another year :(
Sorry for the noise :(
next prev parent reply other threads:[~2026-01-14 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 13:10 [PATCH net-next] net: minor __alloc_skb() optimization Eric Dumazet
2026-01-14 1:44 ` Jakub Kicinski
2026-01-14 1:54 ` Eric Dumazet
2026-01-14 2:01 ` Eric Dumazet
2026-01-14 2:30 ` Jakub Kicinski [this message]
2026-01-16 4:00 ` patchwork-bot+netdevbpf
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=20260113183008.15175891@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@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