• Josef Bacik's avatar
    Btrfs: handle a missing extent for the first file extent · 25a50341
    Josef Bacik authored
    While trying to kill our hole extents I noticed I was seeing problems where we
    seek into a file and then start writing and then try to fiemap that file later.
    This is because we search for offset 0, don't find anything and so back up one
    slot, which puts us at the inode ref or something like that, which means we goto
    not_found and create an extent map for our entire search area.  This isn't quite
    what we want, we want to move forward one slot and see if there is an extent
    there so we can limit our hole extent.  This patch fixes this problem, I will
    add a testcase for this as well.  Thanks,
    Signed-off-by: default avatarJosef Bacik <jbacik@fusionio.com>
    Signed-off-by: default avatarChris Mason <chris.mason@fusionio.com>
    25a50341
inode.c 231 KB