[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174849183349.2759302.11005825928372039491.git-patchwork-notify@kernel.org>
Date: Thu, 29 May 2025 04:10:33 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: <yangtengteng@...edance.com>
Cc: edumazet@...gle.com, kuniyu@...zon.com, pabeni@...hat.com,
willemb@...gle.com, davem@...emloft.net, kuba@...nel.org, horms@...nel.org,
wuyun.abel@...edance.com, shakeel.butt@...ux.dev, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, zhoufeng.zf@...edance.com,
wangdongdong.6@...edance.com, zhangrui.rod@...edance.com,
yangzhenze@...edance.com
Subject: Re: [PATCH net-next v2] Fix sock_exceed_buf_limit not being triggered in
__sk_mem_raise_allocated
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 27 May 2025 11:04:19 +0800 you wrote:
> From: Tengteng Yang <yangtengteng@...edance.com>
>
> When a process under memory pressure is not part of any cgroup and
> the charged flag is false, trace_sock_exceed_buf_limit was not called
> as expected.
>
> This regression was introduced by commit 2def8ff3fdb6 ("sock:
> Code cleanup on __sk_mem_raise_allocated()"). The fix changes the
> default value of charged to true while preserving existing logic.
>
> [...]
Here is the summary with links:
- [net-next,v2] Fix sock_exceed_buf_limit not being triggered in __sk_mem_raise_allocated
https://git.kernel.org/netdev/net/c/8542d6fac25c
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