From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, eric.dumazet@gmail.com,
edumazet@kernel.org, kris.pan@intel.com
Subject: Re: [PATCH v2 net] net: flush skb_defer_nodes in dev_cpu_dead()
Date: Thu, 24 Sep 2026 18:00:11 +0000 [thread overview]
Message-ID: <179027281189.1685480.10772123660048220576.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260923130318.607255-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Sep 2026 13:03:18 +0000 you wrote:
> When a CPU goes offline, dev_cpu_dead() drains its softnet queues
> (completion_queue, output_queue, poll_list, process_queue, and
> input_pkt_queue), but leaves net_hotdata.skb_defer_nodes untouched.
>
> If oldcpu goes offline while holding pending skbs in its
> skb_defer_nodes lists (e.g. below the sysctl_skb_defer_max >> 1 IPI
> threshold, or if the IPI races with CPU teardown), those skbs remain
> stranded until oldcpu is brought back online. If any of these skbs
> hold page_pool fragments, page_pool_destroy() will stall indefinitely
> waiting for inflight pages to be returned when a netdev or driver is
> torn down while oldcpu is offline.
>
> [...]
Here is the summary with links:
- [v2,net] net: flush skb_defer_nodes in dev_cpu_dead()
https://git.kernel.org/netdev/net/c/06e3f54e8b22
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-09-24 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 13:03 [PATCH v2 net] net: flush skb_defer_nodes in dev_cpu_dead() Eric Dumazet
2026-09-24 18: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=179027281189.1685480.10772123660048220576.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=edumazet@kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kris.pan@intel.com \
--cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.