diff options
| author | Kent Overstreet <kent.overstreet@linux.dev> | 2023-02-26 15:48:39 -0500 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2023-10-22 17:09:54 -0400 |
| commit | 747ded6ddfe88eb9644ee0512c061e46fe2fb09d (patch) | |
| tree | 49e3a7fa17faa7c8505192f07d932eed1f79c17a /fs/bcachefs/btree_write_buffer.c?id=747ded6ddfe88eb9644ee0512c061e46fe2fb09d | |
| parent | 39a1ea129a6906a0d6127036222bdb68ec01a277 (diff) | |
bcachefs: Fix for shared paths in write buffer flush
It's possible for bch2_write_buffer_flush_one() to end up with a shared
path, if called from a context that already has a btree iterator
pointing to a key being flushed. We have to be careful when that
happens, since we can't clone a path that holds write locks.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'fs/bcachefs/btree_write_buffer.c?id=747ded6ddfe88eb9644ee0512c061e46fe2fb09d')
0 files changed, 0 insertions, 0 deletions