diff options
| author |   Kent Overstreet <kent.overstreet@linux.dev> | 2024-06-29 22:12:09 -0400 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2024-07-10 09:53:39 -0400 |
| commit | 29f1c1ae6d2fff3bf4f89d265f4a1a7c8ab78a8e (patch) | |
| tree | abbb33d3a2c71e4bdb73ad0e0d794597aaf98965 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | bcachefs: Fix journal getting stuck on a flush commit (diff) | |
| download | wireguard-linux-29f1c1ae6d2fff3bf4f89d265f4a1a7c8ab78a8e.tar.xz wireguard-linux-29f1c1ae6d2fff3bf4f89d265f4a1a7c8ab78a8e.zip | |
closures: fix closure_sync + closure debugging
originally, stack closures were only used synchronously, and with the
original implementation of closure_sync() the ref never hit 0; thus,
closure_put_after_sub() assumes that if the ref hits 0 it's on the debug
list, in debug mode.
that's no longer true with the current implementation of closure_sync,
so we need a new magic so closure_debug_destroy() doesn't pop an assert.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions