diff options
| author |   Tengteng Yang <yangtengteng@bytedance.com> | 2025-05-27 11:04:19 +0800 |
|---|---|---|
| committer |   Jakub Kicinski <kuba@kernel.org> | 2025-05-28 19:07:53 -0700 |
| commit | 8542d6fac25c03b4bf36b2d762cfe60fda8491bb (patch) | |
| tree | f99bc95c8a938a37424a204eb36b90a524e7d098 /scripts/gdb/linux/utils.py | |
| parent | Merge tag 'bpf-next-6.16' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next (diff) | |
| download | wireguard-linux-8542d6fac25c03b4bf36b2d762cfe60fda8491bb.tar.xz wireguard-linux-8542d6fac25c03b4bf36b2d762cfe60fda8491bb.zip | |
Fix sock_exceed_buf_limit not being triggered in __sk_mem_raise_allocated
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.
Fixes: 2def8ff3fdb6 ("sock: Code cleanup on __sk_mem_raise_allocated()")
Signed-off-by: Abel Wu <wuyun.abel@bytedance.com>
Signed-off-by: Tengteng Yang <yangtengteng@bytedance.com>
Link: https://patch.msgid.link/20250527030419.67693-1-yangtengteng@bytedance.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions