f2fs: handle writepage correctly
authorJaegeuk Kim <jaegeuk@kernel.org>
Mon, 30 May 2016 04:18:23 +0000 (21:18 -0700)
committerJaegeuk Kim <jaegeuk@kernel.org>
Fri, 3 Jun 2016 01:05:24 +0000 (18:05 -0700)
commitb230e6cabf9e77e210fe7990fea12f8894af0fc1
tree4983b8e8faf66e5d96d2b7baedf25b8dd3895330
parenteb4246dc12da4a0369a91c10c2dfe8e2b0955818
f2fs: handle writepage correctly

Previously, f2fs_write_data_pages() calls __f2fs_writepage() which calls
f2fs_write_data_page().
If f2fs_write_data_page() returns AOP_WRITEPAGE_ACTIVATE, __f2fs_writepage()
calls mapping_set_error(). But, this should not happen at every time, since
sometimes f2fs_write_data_page() tries to skip writing pages without error.
For example, volatile_write() gives EIO all the time, as Shuoran Liu pointed
out.

Reported-by: Shuoran Liu <liushuoran@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/data.c