On Thu, Feb 13, 2020 at 12:29:50PM +0000, fdmanana@xxxxxxxxxx wrote:
> From: Filipe Manana <fdmanana@xxxxxxxx>
>
> In btrfs_wait_ordered_range() once we find an ordered extent that has
> finished with an error we exit the loop and don't wait for any other
> ordered extents that might be still in progress.
>
> All the users of btrfs_wait_ordered_range() expect that there are no more
> ordered extents in progress after that function returns. So past fixes
> such like the ones from the two following commits:
>
> ff612ba7849964 ("btrfs: fix panic during relocation after ENOSPC before
> writeback happens")
>
> 28aeeac1dd3080 ("Btrfs: fix panic when starting bg cache writeout after
> IO error")
>
> don't work when there are multiple ordered extents in the range.
>
> Fix that by making btrfs_wait_ordered_range() wait for all ordered extents
> even after it finds one that had an error.
>
> Link: https://github.com/kdave/btrfs-progs/issues/228#issuecomment-569777554
> Signed-off-by: Filipe Manana <fdmanana@xxxxxxxx>
Added to misc-next, thanks.
