On Sun, May 30, 2021 at 08:24:05PM +0530, Ritesh Harjani wrote:

We always return 0 even in case of an error in btrfs_mark_extent_written().
Fix it to return proper error value in case of a failure.

Oh right, this looks like it got forgotten, the whole function does the
right thing regarding errors and the callers also handle it.

Signed-off-by: Ritesh Harjani <redacted>
---
Tested fstests with "-g quick" group. No new failure seen.

That won't be probably enough to trigger the error paths but the patch
otherwise looks correct to me. Added to misc-next, thanks.