encrypted-keys: fix rcu and sparse messages
authorMimi Zohar <zohar@linux.vnet.ibm.com>
Tue, 17 Jan 2012 20:40:02 +0000 (20:40 +0000)
committerJames Morris <jmorris@namei.org>
Tue, 17 Jan 2012 23:41:30 +0000 (10:41 +1100)
commit6ac6172a935d1faf7ef259802267657bc0007a62
tree034c1a79a3d401926f6b968eb270d34f561e50f1
parentee0b31a25a010116f44fca6c96f4516d417793dd
encrypted-keys: fix rcu and sparse messages

Enabling CONFIG_PROVE_RCU and CONFIG_SPARSE_RCU_POINTER resulted in
"suspicious rcu_dereference_check() usage!" and "incompatible types
in comparison expression (different address spaces)" messages.

Access the masterkey directly when holding the rwsem.

Changelog v1:
- Use either rcu_read_lock()/rcu_derefence_key()/rcu_read_unlock()
or remove the unnecessary rcu_derefence() - David Howells

Reported-by: Dmitry Kasatkin <dmitry.kasatkin@intel.com>
Signed-off-by: Mimi Zohar <zohar@us.ibm.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: James Morris <jmorris@namei.org>
security/keys/encrypted-keys/encrypted.c
security/keys/encrypted-keys/masterkey_trusted.c