Al Viro acfa4380ef inode->i_op is never NULL ...

We used to have rather schizophrenic set of checks for NULL ->i_op even
though it had been eliminated years ago.  You'd need to go out of your
way to set it to NULL explicitly _and_ a bunch of code would die on
such inodes anyway.  After killing two remaining places that still
did that bogosity, all that crap can go away.

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

cpumask: prepare for iterators to only go to nr_cpu_ids/nr_cpumask_bits.: core

2009-01-01 10:12:15 +10:30

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

integrity: special fs magic

2008-10-13 09:47:43 +11: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