summaryrefslogtreecommitdiff
path: root/fs/dcache.c
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2018-03-28 21:15:09 +0300
committerJaegeuk Kim <jaegeuk@kernel.org>2018-03-28 22:56:49 +0300
commit53fedcc09c66c68e0fa7ccef0fe9c15f96dca452 (patch)
tree45ec4808b2ec2601e8dcf6bbc74ba736b463b230 /fs/dcache.c
parentd21b0f238adf4641a72f4b0dd4a2b10aa36d09f5 (diff)
downloadlinux-53fedcc09c66c68e0fa7ccef0fe9c15f96dca452.tar.xz
f2fs: reserve bits for fs-verity
Reserve an F2FS feature flag and inode flag for fs-verity. This is an in-development feature that is planned be discussed at LSF/MM 2018 [1]. It will provide file-based integrity and authenticity for read-only files. Most code will be in a filesystem-independent module, with smaller changes needed to individual filesystems that opt-in to supporting the feature. An early prototype supporting F2FS is available [2]. Reserving the F2FS on-disk bits for fs-verity will prevent users of the prototype from conflicting with other new F2FS features. Note that we're reserving the inode flag in f2fs_inode.i_advise, which isn't really appropriate since it's not a hint or advice. But ->i_advise is already being used to hold the 'encrypt' flag; and F2FS's ->i_flags uses the generic FS_* values, so it seems ->i_flags can't be used for an F2FS-specific flag without additional work to remove the assumption that ->i_flags uses the generic flags namespace. [1] https://marc.info/?l=linux-fsdevel&m=151690752225644 [2] https://git.kernel.org/pub/scm/linux/kernel/git/mhalcrow/linux.git/log/?h=fs-verity-dev Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/dcache.c')
0 files changed, 0 insertions, 0 deletions