[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175288380777.2831723.3410083035136520170.git-patchwork-notify@kernel.org>
Date: Sat, 19 Jul 2025 00:10:07 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jesper Dangaard Brouer <hawk@...nel.org>
Cc: netdev@...r.kernel.org, kuba@...nel.org, bpf@...r.kernel.org,
eric.dumazet@...il.com, davem@...emloft.net, pabeni@...hat.com, toke@...e.dk,
kernel-team@...udflare.com, mfleming@...udflare.com
Subject: Re: [PATCH net-next V5] net: track pfmemalloc drops via
SKB_DROP_REASON_PFMEMALLOC
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 16 Jul 2025 18:26:53 +0200 you wrote:
> Add a new SKB drop reason (SKB_DROP_REASON_PFMEMALLOC) to track packets
> dropped due to memory pressure. In production environments, we've observed
> memory exhaustion reported by memory layer stack traces, but these drops
> were not properly tracked in the SKB drop reason infrastructure.
>
> While most network code paths now properly report pfmemalloc drops, some
> protocol-specific socket implementations still use sk_filter() without
> drop reason tracking:
> - Bluetooth L2CAP sockets
> - CAIF sockets
> - IUCV sockets
> - Netlink sockets
> - SCTP sockets
> - Unix domain sockets
>
> [...]
Here is the summary with links:
- [net-next,V5] net: track pfmemalloc drops via SKB_DROP_REASON_PFMEMALLOC
https://git.kernel.org/netdev/net-next/c/a6f190630d07
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists