f2fs crypto: add filename encryption for roll-forward recovery
authorJaegeuk Kim <jaegeuk@kernel.org>
Thu, 30 Apr 2015 00:02:18 +0000 (17:02 -0700)
committerJaegeuk Kim <jaegeuk@kernel.org>
Thu, 28 May 2015 22:41:55 +0000 (15:41 -0700)
commite7d5545285ededcf73dc7cbb9b7c65d0259f2b44
treee326305090c249a5cfe26e1347bc63cba6ba898d
parent6e22c691ba0a63ba89f516f0bf1828cf6dce372d
f2fs crypto: add filename encryption for roll-forward recovery

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>
fs/f2fs/dir.c
fs/f2fs/f2fs.h
fs/f2fs/file.c
fs/f2fs/namei.c
fs/f2fs/recovery.c
This page took 0.025136 seconds and 5 git commands to generate.