diff options
| author | Kent Overstreet <[email protected]> | 2022-09-02 22:59:39 -0400 |
|---|---|---|
| committer | Kent Overstreet <[email protected]> | 2023-10-22 17:09:40 -0400 |
| commit | 38474c264252475196a5e3c555b2625a5bc36a00 (patch) | |
| tree | 68d8bbf34a8bf3a3548b0e2c09bbd6d38bbeedee /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 3d21d48e898a2eadc9055c44e0fd51e6087c9e9f (diff) | |
bcachefs: Avoid using btree_node_lock_nopath()
With the upcoming cycle detector, we have to be careful about using
btree_node_lock_nopath - in particular, using it to take write locks can
cause deadlocks.
All held locks need to be tracked in a btree_path, so that the cycle
detector knows about them - unless we know that we cannot cause
deadlocks for other reasons: e.g. we are only taking read locks, or
we're in very early fsck (topology repair).
Signed-off-by: Kent Overstreet <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions