UPSTREAM: f2fs: avoid fsync() failure caused by EAGAIN in writepage()
authorJaegeuk Kim <jaegeuk@kernel.org>
Fri, 4 May 2018 06:26:02 +0000 (23:26 -0700)
committerJaegeuk Kim <jaegeuk@google.com>
Tue, 8 May 2018 00:04:57 +0000 (17:04 -0700)
pageout() in MM traslates EAGAIN, so calls handle_write_error()
 -> mapping_set_error() -> set_bit(AS_EIO, ...).
 file_write_and_wait_range() will see EIO error, which is critical
 to return value of fsync() followed by atomic_write failure to user.

Change-Id: Ifdd5e09defcf0705901ff7f23001d68a811da3af
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
(cherry picked from commit 1ccd6c4ff9ccd74bb87903067618815d326af242)

fs/f2fs/data.c

index 1afce941a9dfd801a67d02988cec3879d064b681..c9db73e498a6a0b3ccff569bf8a04d1d20c09b1d 100644 (file)
@@ -1905,7 +1905,13 @@ out:
 
 redirty_out:
        redirty_page_for_writepage(wbc, page);
-       if (!err)
+       /*
+        * pageout() in MM traslates EAGAIN, so calls handle_write_error()
+        * -> mapping_set_error() -> set_bit(AS_EIO, ...).
+        * file_write_and_wait_range() will see EIO error, which is critical
+        * to return value of fsync() followed by atomic_write failure to user.
+        */
+       if (!err || wbc->for_reclaim)
                return AOP_WRITEPAGE_ACTIVATE;
        unlock_page(page);
        return err;