* [PATCH v2] Yama: access task_struct->comm directly
@ 2012-08-15 18:41 Kees Cook
2012-08-16 16:56 ` Oleg Nesterov
0 siblings, 1 reply; 2+ messages in thread
From: Kees Cook @ 2012-08-15 18:41 UTC (permalink / raw)
To: linux-kernel
Cc: James Morris, Fengguang Wu, Oleg Nesterov, Kees Cook,
John Johansen, linux-security-module
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>
---
v2: update with newly added traceme report.
---
security/yama/yama_lsm.c | 10 ++--------
1 files changed, 2 insertions(+), 8 deletions(-)
diff --git a/security/yama/yama_lsm.c b/security/yama/yama_lsm.c
index d51b7c7..0cc99a3 100644
--- a/security/yama/yama_lsm.c
+++ b/security/yama/yama_lsm.c
@@ -279,12 +279,9 @@ static int yama_ptrace_access_check(struct task_struct *child,
}
if (rc) {
- char name[sizeof(current->comm)];
printk_ratelimited(KERN_NOTICE
"ptrace of pid %d was attempted by: %s (pid %d)\n",
- child->pid,
- get_task_comm(name, current),
- current->pid);
+ child->pid, current->comm, current->pid);
}
return rc;
@@ -319,12 +316,9 @@ static int yama_ptrace_traceme(struct task_struct *parent)
}
if (rc) {
- char name[sizeof(current->comm)];
printk_ratelimited(KERN_NOTICE
"ptraceme of pid %d was attempted by: %s (pid %d)\n",
- current->pid,
- get_task_comm(name, parent),
- parent->pid);
+ current->pid, parent->comm, parent->pid);
}
return rc;
--
1.7.0.4
--
Kees Cook
Chrome OS Security
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v2] Yama: access task_struct->comm directly
2012-08-15 18:41 [PATCH v2] Yama: access task_struct->comm directly Kees Cook
@ 2012-08-16 16:56 ` Oleg Nesterov
0 siblings, 0 replies; 2+ messages in thread
From: Oleg Nesterov @ 2012-08-16 16:56 UTC (permalink / raw)
To: Kees Cook
Cc: linux-kernel, James Morris, Fengguang Wu, John Johansen,
linux-security-module
On 08/15, Kees Cook wrote:
>
> v2: update with newly added traceme report.
...
> @@ -319,12 +316,9 @@ static int yama_ptrace_traceme(struct task_struct *parent)
> }
>
> if (rc) {
> - char name[sizeof(current->comm)];
> printk_ratelimited(KERN_NOTICE
> "ptraceme of pid %d was attempted by: %s (pid %d)\n",
> - current->pid,
> - get_task_comm(name, parent),
> - parent->pid);
> + current->pid, parent->comm, parent->pid);
Hmm, yes. This change is even more important. This is called under
write_lock_irq(tasklist_lock), task_lock() can deadlock if we race
with another CPU doing task_lock()->interrupt->read_lock(tasklist).
Oleg.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-08-16 18:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-15 18:41 [PATCH v2] Yama: access task_struct->comm directly Kees Cook
2012-08-16 16:56 ` Oleg Nesterov
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.