diff options
| author | Chao Yu | 2019-02-19 09:23:53 +0100 |
|---|---|---|
| committer | Jaegeuk Kim | 2019-03-13 02:59:17 +0100 |
| commit | aa2c8c43e4a5c242f5b0331c8b7a941b85f9435a (patch) | |
| tree | 770a3dd298dc739d2b3b1aecdfd21316d54d8993 /firmware | |
| parent | f2fs: silence VM_WARN_ON_ONCE in mempool_alloc (diff) | |
| download | kernel-qcow2-linux-aa2c8c43e4a5c242f5b0331c8b7a941b85f9435a.tar.gz kernel-qcow2-linux-aa2c8c43e4a5c242f5b0331c8b7a941b85f9435a.tar.xz kernel-qcow2-linux-aa2c8c43e4a5c242f5b0331c8b7a941b85f9435a.zip | |
f2fs: fix to retry fill_super only if recovery failed
With current retry mechanism in f2fs_fill_super, first fill_super
fails due to no memory, then second fill_super runs w/o recovery,
if we succeed, we may lose fsynced data, it doesn't make sense.
Let's retry fill_super only if it occurs non-ENOMEM error during
recovery.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions