android_kernel_xiaomi_sm8350/security
Al Viro 56ff5efad9 zero i_uid/i_gid on inode allocation
... and don't bother in callers.  Don't bother with zeroing i_blocks,
while we are at it - it's already been zeroed.

i_mode is not worth the effort; it has no common default value.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2009-01-05 11:54:28 -05:00
..
keys KEYS: Fix variable uninitialisation warnings 2008-12-29 14:24:43 +11:00
selinux zero i_uid/i_gid on inode allocation 2009-01-05 11:54:28 -05:00
smack smackfs: check for allocation failures in smk_set_access() 2008-12-25 12:14:55 +11:00
capability.c introduce new LSM hooks where vfsmount is available. 2008-12-31 18:07:37 -05:00
commoncap.c inode->i_op is never NULL 2009-01-05 11:54:28 -05:00
device_cgroup.c devcgroup: remove spin_lock() 2008-10-20 08:52:38 -07:00
inode.c zero i_uid/i_gid on inode allocation 2009-01-05 11:54:28 -05:00
Kconfig introduce new LSM hooks where vfsmount is available. 2008-12-31 18:07:37 -05:00
Makefile securityfs: do not depend on CONFIG_SECURITY 2008-08-28 10:47:42 +10:00
root_plug.c CRED: Make execve() take advantage of copy-on-write credentials 2008-11-14 10:39:24 +11:00
security.c introduce new LSM hooks where vfsmount is available. 2008-12-31 18:07:37 -05:00