aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/python
diff options
context:
space:
mode:
authorKuniyuki Iwashima <kuniyu@google.com>2026-11-04 16:27:56 +0000
committerJakub Kicinski <kuba@kernel.org>2026-11-09 17:17:56 -0800
commit0edbc945eb9edd0086f25b151a79cfe4adc0dfa8 (patch)
tree9b39c875050a2096db5883e6fa4e5d2e648c086d /tools/perf/python
parentMAINTAINERS: remove and replace myself as sfc maintainer (diff)
af_unix: Remove gc_in_progress check in unix_peek_fpl().
unix_vertex_dead() and unix_peek_fpl() are synchronised with unix_peek_seq to prevent GC from purging a live socket's recvq. unix_peek_fpl() skips the synchronisation if gc_in_progress is false. However, on weakly ordered arch, GC might have already started working while the write to gc_in_progress is buffered. This does not occur on x86. This is an unlikely path that happens only when AF_UNIX fd is peeked so not worth complicating. Instead of adding memory barriers in unix_gc() and unix_peek_fpl(), let's simply remove the broken short-circuit. Fixes: e5b31d988a41 ("af_unix: Give up GC if MSG_PEEK intervened.") Reported-by: Qihang Tang <q.h.hack.winter@gmail.com> Signed-off-by: Kuniyuki Iwashima <kuniyu@google.com> Link: https://patch.msgid.link/20261104162858.991930-1-kuniyu@google.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/python')
0 files changed, 0 insertions, 0 deletions