aboutsummaryrefslogtreecommitdiffstats
path: root/fs/btrfs/transaction.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@toxicpanda.com>2019-03-06 17:13:04 -0500
committerDavid Sterba <dsterba@suse.com>2019-03-13 17:13:32 +0100
commit2cc8334270e281815c3850c3adea363c51f21e0d (patch)
tree4d0dbb78a4c8e8ecd04f0b598d703330fc4462d9 /fs/btrfs/transaction.c
parentBtrfs: fix incorrect file size after shrinking truncate and fsync (diff)
downloadlinux-dev-2cc8334270e281815c3850c3adea363c51f21e0d.tar.xz
linux-dev-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: stable@vger.kernel.org # 4.4+ Reviewed-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: Josef Bacik <josef@toxicpanda.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/transaction.c')
0 files changed, 0 insertions, 0 deletions