f2fs: fix to do security initialization of encrypted inode with original filename

Browse source

When creating new inode, security_inode_init_security will be called for
initializing security info related to the inode, and filename is passed to
security module, it helps security module such as SElinux to know which
rule or label could be applied for the inode with specified name.

Previously, if new inode is created as an encrypted one, f2fs will transfer
encrypted filename to security module which may fail the check of security
policy belong to the inode. So in order to this issue, alter to transfer
original unencrypted filename instead.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

...

This commit is contained in:

Chao Yu 2016-08-28 18:57:55 +08:00 • committed by Jaegeuk Kim

parent 7ea984b060

commit 9421d57051

3 changed files with 26 additions and 20 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

21

fs/f2fs/dir.c

View file

8

fs/f2fs/f2fs.h

View file

17

fs/f2fs/inline.c

View file