diff options
| author |   Mimi Zohar <zohar@linux.vnet.ibm.com> | 2012-01-17 20:40:02 +0000 |
|---|---|---|
| committer |   James Morris <jmorris@namei.org> | 2012-01-18 10:41:30 +1100 |
| commit | 6ac6172a935d1faf7ef259802267657bc0007a62 (patch) | |
| tree | 034c1a79a3d401926f6b968eb270d34f561e50f1 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | keys: fix trusted/encrypted keys sparse rcu_assign_pointer messages (diff) | |
| download | wireguard-linux-6ac6172a935d1faf7ef259802267657bc0007a62.tar.xz wireguard-linux-6ac6172a935d1faf7ef259802267657bc0007a62.zip | |
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>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions