Kees Cook 7612bfeecc Yama: access task_struct->comm directly ... The core ptrace access checking routine holds a task lock, and when reporting a failure, Yama takes a separate task lock. To avoid a potential deadlock with two ptracers taking the opposite locks, do not use get_task_comm() and just use ->comm directly since accuracy is not important for the report. Reported-by: Fengguang Wu <fengguang.wu@intel.com> Suggested-by: Oleg Nesterov <oleg@redhat.com> CC: stable@vger.kernel.org Signed-off-by: Kees Cook <keescook@chromium.org> Acked-by: John Johansen <john.johansen@canonical.com> Signed-off-by: James Morris <james.l.morris@oracle.com>		2012-08-17 20:40:38 +10:00
..
apparmor
integrity
keys	Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security	2012-07-23 18:49:06 -07:00
selinux	selinux: tag avc cache alloc as non-critical	2012-07-31 18:42:47 -07:00
smack	smack: off by one error	2012-07-30 15:04:17 +10:00
tomoyo
yama	Yama: access task_struct->comm directly	2012-08-17 20:40:38 +10:00
capability.c
commoncap.c
device_cgroup.c
inode.c
Kconfig
lsm_audit.c
Makefile
min_addr.c
security.c