f2fs crypto: add filename encryption for roll-forward recovery

Browse source

This patch adds a bit flag to indicate whether or not i_name in the inode
is encrypted.

If this name is encrypted, we can't do recover_dentry during roll-forward.
So, f2fs_sync_file() needs to do checkpoint, if this will be needed in future.

Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

...

This commit is contained in:

Jaegeuk Kim 2015-04-29 17:02:18 -07:00

parent 6e22c691ba

commit e7d5545285

5 changed files with 41 additions and 9 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

8

fs/f2fs/dir.c

View file

5

fs/f2fs/f2fs.h

View file

4

fs/f2fs/file.c

View file

20

fs/f2fs/namei.c

View file

13

fs/f2fs/recovery.c

View file