mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	almasrymina@google.com, daniel@iogearbox.net, willemb@google.com,
	willemdebruijn.kernel@gmail.com, mst@redhat.com,
	jasowangio@gmail.com, eperezma@redhat.com,
	narcisav.kernel@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] net: do not run out of frags in alloc_skb_with_frags()
Date: Sat, 21 Nov 2026 22:30:05 +0000	[thread overview]
Message-ID: <179530020578.1192635.2530675311737257518.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116115620.18151-1-yanhaishuang@cmss.chinamobile.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 16 Nov 2026 20:56:18 +0900 you wrote:
> alloc_skb_with_frags() can fail with -ENOBUFS for a data_len that passed
> its size check. Patch 1 fixes it, patch 2 adds a KUnit test.
> 
> The issues were found with the help of an AI coding assistant.
> 
> Changes in v3:
> - Patch 1: check the frags left only after a failed allocation, with a
>   shift (Eric).
> - Patch 1: say that the allocation still fails if the retry fails.
> - Patch 2: skip only if MAX_SKB_FRAGS - 1 order-3 pages can't be held
>   at once; one page was nearly always available (netdev AI review).
> - Shorter changelogs (Eric).
> 
> [...]

Here is the summary with links:
  - [net,v3,1/2] net: do not run out of frags in alloc_skb_with_frags()
    https://git.kernel.org/netdev/net/c/5924465bb4e9
  - [net,v3,2/2] net: add a KUnit test for the alloc_skb_with_frags() tail split
    https://git.kernel.org/netdev/net/c/e8c39bfac24d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-21 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 11:56 Haishuang Yan
2026-11-16 11:56 ` [PATCH net v3 1/2] " Haishuang Yan
2026-11-19 14:56   ` netdev-bot+sashiko
2026-11-16 11:56 ` [PATCH net v3 2/2] net: add a KUnit test for the alloc_skb_with_frags() tail split Haishuang Yan
2026-11-19 14:56   ` netdev-bot+sashiko
2026-11-20  7:40     ` Haishuang Yan
2026-11-21 22:30 ` 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=179530020578.1192635.2530675311737257518.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=almasrymina@google.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=eperezma@redhat.com \
    --cc=horms@kernel.org \
    --cc=jasowangio@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=narcisav.kernel@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=yanhaishuang@cmss.chinamobile.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®