diff options
| author | Josef Bacik <[email protected]> | 2019-03-06 22:13:04 +0000 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2019-03-13 16:13:32 +0000 |
| commit | 2cc8334270e281815c3850c3adea363c51f21e0d (patch) | |
| tree | 4d0dbb78a4c8e8ecd04f0b598d703330fc4462d9 /tools/perf/scripts/python/check-perf-trace.py | |
| parent | Btrfs: fix incorrect file size after shrinking truncate and fsync (diff) | |
| download | kernel-2cc8334270e281815c3850c3adea363c51f21e0d.tar.gz kernel-2cc8334270e281815c3850c3adea363c51f21e0d.zip | |
btrfs: remove WARN_ON in log_dir_items
When Filipe added the recursive directory logging stuff in
2f2ff0ee5e430 ("Btrfs: fix metadata inconsistencies after directory
fsync") he specifically didn't take the directory i_mutex for the
children directories that we need to log because of lockdep. This is
generally fine, but can lead to this WARN_ON() tripping if we happen to
run delayed deletion's in between our first search and our second search
of dir_item/dir_indexes for this directory. We expect this to happen,
so the WARN_ON() isn't necessary. Drop the WARN_ON() and add a comment
so we know why this case can happen.
CC: [email protected] # 4.4+
Reviewed-by: Filipe Manana <[email protected]>
Signed-off-by: Josef Bacik <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions