Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski [off-list ref]:

On Mon, 29 Jun 2026 04:45:39 -0700 you wrote:

Both netconsole and netpoll keep a small preallocated pool of skbs
(skb_pool) so they can still get a buffer under memory pressure.

On the hot path they first attempt a normal GFP_ATOMIC allocation and only
fall back to the pool when that fails, keeping the pool as a last resort.

This is where the problem happens. If alloc_skb() fails, we now have
more than 100 message coming from the page=0 failure, which consumes the
scarce pool of skb, making the real issue disappear.

[...]

Here is the summary with links:
  - [net-next,1/2] netconsole: do not warn when the best-effort skb allocation fails
    https://git.kernel.org/netdev/net-next/c/09f7a613a14f
  - [net-next,2/2] netpoll: do not warn when the best-effort pool refill fails
    https://git.kernel.org/netdev/net-next/c/84c0ff1efb62

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