summaryrefslogtreecommitdiffstats
path: root/fs/dlm/plock.c
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fusionio.com>2012-09-19 15:42:38 -0400
committerChris Mason <chris.mason@fusionio.com>2012-10-08 20:09:02 -0400
commit0aa4a17d8232e7d8a42763b53bb9943bc0484b18 (patch)
treefa3ca49da139088f2aad0877944f06e4bec1b6fb /fs/dlm/plock.c
parent005d6427ac4f276d937a36ca6a1d62b181ed70bf (diff)
downloadlinux-0aa4a17d8232e7d8a42763b53bb9943bc0484b18.tar.bz2
Btrfs: handle not finding the extent exactly when logging changed extents
I started hitting warnings when running xfstest 68 in a loop because there were EM's that were not lined up properly with the physical extents. This is ok, if we do something like punch a hole or write to a preallocated space or something like that we can have an EM that doesn't cover the entire physical extent. So fix the tree logging stuff to cope with this case so we don't just commit the transaction. With this patch I no longer see the warnings from the tree logging code. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'fs/dlm/plock.c')
0 files changed, 0 insertions, 0 deletions