diff options
| author | Sheng Yong | 2018-03-15 11:51:41 +0100 |
|---|---|---|
| committer | Jaegeuk Kim | 2018-03-17 06:02:47 +0100 |
| commit | b7c409deda6bcaaa6452b015937a013dd8b481b4 (patch) | |
| tree | 5da0435f1eb10a51ff068c2793dac3512bb6778d /fs/f2fs/namei.c | |
| parent | f2fs: release locks before return in f2fs_ioc_gc_range() (diff) | |
| download | kernel-qcow2-linux-b7c409deda6bcaaa6452b015937a013dd8b481b4.tar.gz kernel-qcow2-linux-b7c409deda6bcaaa6452b015937a013dd8b481b4.tar.xz kernel-qcow2-linux-b7c409deda6bcaaa6452b015937a013dd8b481b4.zip | |
f2fs: introduce F2FS_FEATURE_LOST_FOUND feature
This patch introduces a new feature, F2FS_FEATURE_LOST_FOUND, which
is set by mkfs. mkfs creates a directory named lost+found, which saves
unreachable files. If fsck finds a file which has no parent, or its
parent is removed by fsck, the file will be placed under lost+found
directory by fsck.
lost+found directory could not be encrypted. As a result, the root
directory cannot be encrypted too. So if LOST_FOUND feature is enabled,
let's avoid to encrypt root directory.
Signed-off-by: Sheng Yong <shengyong1@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/namei.c')
0 files changed, 0 insertions, 0 deletions