btrfs: extent_io: Handle errors better in extent_write_locked_range()
authorQu Wenruo <wqu@suse.com>
Wed, 20 Mar 2019 06:27:45 +0000 (14:27 +0800)
committerDavid Sterba <dsterba@suse.com>
Mon, 29 Apr 2019 17:02:23 +0000 (19:02 +0200)
commit02c6db4f7308e4f5adf4df2ef623160bfdb18636
tree85379fcdf5e29d492e5f99166c14bb41db1c768e
parente06808be8a5296c09be84b3aaf63087b5737ba16
btrfs: extent_io: Handle errors better in extent_write_locked_range()

We can only get @ret <= 0.  Add an ASSERT() for it just in case.

Then, instead of submitting the write bio even we got some error, check
the return value first.

If we have already hit some error, just clean up the corrupted or
half-baked bio, and return error.

If there is no error so far, then call flush_write_bio() and return the
result.

Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent_io.c