On Fri, 2019-05-03 at 16:25 +0100, Filipe Manana wrote: > On Fri, May 3, 2019 at 4:21 PM Josef Bacik <[email protected]> > wrote: > > If we have an error writing out a delalloc range in > > btrfs_punch_hole_lock_range we'll unlock the inode and then goto > > out_only_mutex, where we will again unlock the inode. This is bad, > > don't do this. > > > > Signed-off-by: Josef Bacik <[email protected]> > > Reviewed-by: Filipe Manana <[email protected]> > > Looks good, I introduced the double unlock accidentally.
Does the patch need a Fixes: tag so the -stable people know how far to backport it?
