btrfs: fix incorrect error return ret being passed to mapping_set_error
authorColin Ian King <colin.king@canonical.com>
Tue, 9 May 2017 17:14:01 +0000 (18:14 +0100)
committerDavid Sterba <dsterba@suse.com>
Tue, 16 May 2017 13:42:10 +0000 (15:42 +0200)
The setting of return code ret should be based on the error code
passed into function end_extent_writepage and not on ret. Thanks
to Liu Bo for spotting this mistake in the original fix I submitted.

Detected by CoverityScan, CID#1414312 ("Logically dead code")

Fixes: 5dca6eea91653e ("Btrfs: mark mapping with error flag to report errors to userspace")
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent_io.c

index 4317ed3ad83039428c85a1635e104e6cf6b8b364..d3619e01000551c42bf65bd6983801a0b04423e5 100644 (file)
@@ -2458,7 +2458,7 @@ void end_extent_writepage(struct page *page, int err, u64 start, u64 end)
        if (!uptodate) {
                ClearPageUptodate(page);
                SetPageError(page);
-               ret = ret < 0 ? ret : -EIO;
+               ret = err < 0 ? err : -EIO;
                mapping_set_error(page->mapping, ret);
        }
 }