IMA: use inode->i_lock to protect read and write counters
authorEric Paris <eparis@redhat.com>
Mon, 25 Oct 2010 18:41:45 +0000 (14:41 -0400)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 26 Oct 2010 18:37:18 +0000 (11:37 -0700)
commitad16ad00c34d3f320a5876b3d711ef6bc81362e1
tree7cf3b755567fde2850d2ea7f4a186a0dcea6b80f
parent15aac676778f206b42c4d7782b08f89246680485
IMA: use inode->i_lock to protect read and write counters

Currently IMA used the iint->mutex to protect the i_readcount and
i_writecount.  This patch uses the inode->i_lock since we are going to
start using in inode objects and that is the most appropriate lock.

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>
security/integrity/ima/ima.h
security/integrity/ima/ima_main.c