diff options
| author | Jaegeuk Kim <jaegeuk@kernel.org> | 2016-05-29 21:18:23 -0700 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2016-06-02 18:05:24 -0700 |
| commit | b230e6cabf9e77e210fe7990fea12f8894af0fc1 (patch) | |
| tree | 4983b8e8faf66e5d96d2b7baedf25b8dd3895330 /samples/kfifo | |
| parent | eb4246dc12da4a0369a91c10c2dfe8e2b0955818 (diff) | |
| download | linux-stable-b230e6cabf9e77e210fe7990fea12f8894af0fc1.tar.gz linux-stable-b230e6cabf9e77e210fe7990fea12f8894af0fc1.tar.bz2 linux-stable-b230e6cabf9e77e210fe7990fea12f8894af0fc1.zip | |
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>
Diffstat (limited to 'samples/kfifo')
0 files changed, 0 insertions, 0 deletions