diff options
| author | Oleg Nesterov <oleg@redhat.com> | 2013-12-23 17:45:01 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-01-09 15:24:20 -0500 |
| commit | 2b25925431bfedfbd1b234afcadbcdf4f09901f8 (patch) | |
| tree | 9c923c41a91e3a0be26ec58eb0dff090c5aa067d /crypto/ccm.c | |
| parent | faecbbe4213acc9da2aa44d0577cad1a9f419946 (diff) | |
selinux: selinux_setprocattr()->ptrace_parent() needs rcu_read_lock()
commit c0c1439541f5305b57a83d599af32b74182933fe upstream.
selinux_setprocattr() does ptrace_parent(p) under task_lock(p),
but task_struct->alloc_lock doesn't pin ->parent or ->ptrace,
this looks confusing and triggers the "suspicious RCU usage"
warning because ptrace_parent() does rcu_dereference_check().
And in theory this is wrong, spin_lock()->preempt_disable()
doesn't necessarily imply rcu_read_lock() we need to access
the ->parent.
Reported-by: Evan McNabb <emcnabb@redhat.com>
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Paul Moore <pmoore@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto/ccm.c')
0 files changed, 0 insertions, 0 deletions