diff options
| author | Kuniyuki Iwashima <kuniyu@google.com> | 2025-08-15 23:16:12 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2025-08-20 05:20:59 +0300 |
| commit | 9d85c565a7b7c78b732393c02bcaa4d5c275fe58 (patch) | |
| tree | e35c47c42f8ead6bd9a739eb84fcee42c3b2a1e9 /tools/perf/scripts/python/syscall-counts.py | |
| parent | e2afa83296bbac40829624b508492b562a21e4d4 (diff) | |
| download | linux-9d85c565a7b7c78b732393c02bcaa4d5c275fe58.tar.xz | |
net: Call trace_sock_exceed_buf_limit() for memcg failure with SK_MEM_RECV.
Initially, trace_sock_exceed_buf_limit() was invoked when
__sk_mem_raise_allocated() failed due to the memcg limit or the
global limit.
However, commit d6f19938eb031 ("net: expose sk wmem in
sock_exceed_buf_limit tracepoint") somehow suppressed the event
only when memcg failed to charge for SK_MEM_RECV, although the
memcg failure for SK_MEM_SEND still triggers the event.
Let's restore the event for SK_MEM_RECV.
Signed-off-by: Kuniyuki Iwashima <kuniyu@google.com>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Shakeel Butt <shakeel.butt@linux.dev>
Link: https://patch.msgid.link/20250815201712.1745332-5-kuniyu@google.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions
