diff options
| author | Jaegeuk Kim <jaegeuk.kim@samsung.com> | 2013-03-20 19:01:06 +0900 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk.kim@samsung.com> | 2013-03-27 09:16:06 +0900 |
| commit | 6ead114232f786e3ef7a034c8617f2a4df8e5226 (patch) | |
| tree | 4ce177b708f8e98b148658a21d35fbec8bdc1e6b /fs/f2fs/f2fs.h | |
| parent | 111d2495a8a8fbd8e3bb0f1c1c60f977b1386249 (diff) | |
| download | linux-6ead114232f786e3ef7a034c8617f2a4df8e5226.tar.bz2 | |
f2fs: fix the recovery flow to handle errors correctly
We should handle errors during the recovery flow correctly.
For example, if we get -ENOMEM, we should report a mount failure instead of
conducting the remained mount procedure.
Reviewed-by: Namjae Jeon <namjae.jeon@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'fs/f2fs/f2fs.h')
| -rw-r--r-- | fs/f2fs/f2fs.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 5bb87e0216f5..109e12d21a36 100644 --- a/fs/f2fs/f2fs.h +++ b/fs/f2fs/f2fs.h @@ -1027,7 +1027,7 @@ void destroy_gc_caches(void); /* * recovery.c */ -void recover_fsync_data(struct f2fs_sb_info *); +int recover_fsync_data(struct f2fs_sb_info *); bool space_for_roll_forward(struct f2fs_sb_info *); /* |