diff options
| author | Jaegeuk Kim <jaegeuk@kernel.org> | 2016-05-29 21:18:23 -0700 |
|---|---|---|
| committer | Mister Oyster <oysterized@gmail.com> | 2017-04-13 12:33:42 +0200 |
| commit | c6f1748b410c15745ab5f69d993940dfdee85ca0 (patch) | |
| tree | 713a4b2910278e1e563a7b25fd7ba48096c05649 /include/linux/asn1_ber_bytecode.h | |
| parent | c9290cabee18f3cfa3a9916fbfc11eea7f71c9b8 (diff) | |
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 'include/linux/asn1_ber_bytecode.h')
0 files changed, 0 insertions, 0 deletions