linux-next

mirror of https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git synced 2025-01-15 11:07:46 +00:00

History

Oleg Nesterov 465954cd64 selinux: selinux_setprocattr()->ptrace_parent() needs rcu_read_lock()

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>
Cc: stable@vger.kernel.org
Signed-off-by: Paul Moore <pmoore@redhat.com>

2013-12-16 16:00:29 -05:00

apparmor

apparmor: fix bad lock balance when introspecting policy

2013-10-16 11:54:01 +11:00

integrity

xattr: Constify ->name member of "struct xattr".

2013-07-25 19:30:03 +10:00

keys

aio: don't include aio.h in sched.h

2013-05-07 20:16:25 -07:00

selinux

selinux: selinux_setprocattr()->ptrace_parent() needs rcu_read_lock()