IMA: explicit IMA i_flag to remove global lock on inode_delete
authorEric Paris <eparis@redhat.com>
Mon, 25 Oct 2010 18:42:19 +0000 (14:42 -0400)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 26 Oct 2010 18:37:19 +0000 (11:37 -0700)
commit196f518128d2ee6e0028b50e6fec0313640db142
tree43a1d76bee477dbaa682233979e86f58a98369f0
parent64c62f06bef8314a64d3189cb9c78062d54169b3
IMA: explicit IMA i_flag to remove global lock on inode_delete

Currently for every removed inode IMA must take a global lock and search
the IMA rbtree looking for an associated integrity structure.  Instead
we explicitly mark an inode when we add an integrity structure so we
only have to take the global lock and do the removal if it exists.

Signed-off-by: Eric Paris <eparis@redhat.com>
Acked-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
include/linux/fs.h
security/integrity/ima/ima_iint.c
security/integrity/ima/ima_main.c