diff options
| author | Chao Yu <yuchao0@huawei.com> | 2019-02-19 16:23:53 +0800 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2019-03-14 13:57:38 -0700 |
| commit | 9878080f02d67df945dd34fd56cc6b41df002704 (patch) | |
| tree | ca03f91209ca6f3ef134760f7786b1d1c9c84878 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 7307334f43684753f9bd4228a126d57cd20d6c1e (diff) | |
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 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions
