Btrfs: fix hole check in log_one_extent
authorJosef Bacik <jbacik@fusionio.com>
Mon, 14 Oct 2013 21:23:08 +0000 (17:23 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 20 Dec 2013 15:49:08 +0000 (07:49 -0800)
commit63e431def463a8c620d1b03c77d440c6903917d1
treecbdd599b24cac6fb1bd138ef22663f7e458a649a
parent4ae8656075c351ba3a3aefc923550ef2b7280164
Btrfs: fix hole check in log_one_extent

commit ed9e8af88e2551aaa6bf51d8063a2493e2d71597 upstream.

I added an assert to make sure we were looking up aligned offsets for csums and
I tripped it when running xfstests.  This is because log_one_extent was checking
if block_start == 0 for a hole instead of EXTENT_MAP_HOLE.  This worked out fine
in practice it seems, but it adds a lot of extra work that is uneeded.  With
this fix I'm no longer tripping my assert.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/btrfs/tree-log.c