From: Oleg Nesterov <oleg@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH 01/12 v3] ptrace: ptrace_signal: fix the usage of ->parent
Date: Sun, 31 May 2009 00:38:24 +0200 [thread overview]
Message-ID: <20090530223824.GA30478@redhat.com> (raw)
This patch complicates the code to fix the pure theoretical problems.
But since we are going to change this code, it is better to fix them
anyway.
- If we are not traced any longer after ptrace_stop(), si_pid/si_uid
are not necessary right.
- It is not safe to dereference current->parent without tasklist or
RCU lock. The tracer can detach and exit. ->siglock can't prevent
this, and (in theory) local_irq_disable() doesn't imply RCU lock.
Hopefully this "signr != info->si_signo" code will go away eventually.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
---
kernel/signal.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
--- PTRACE/kernel/signal.c~01_PTRACE_SIGNAL 2009-05-30 21:30:04.000000000 +0200
+++ PTRACE/kernel/signal.c 2009-05-30 21:52:00.000000000 +0200
@@ -1770,11 +1770,22 @@ static int ptrace_signal(int signr, sigi
specific in the siginfo structure then it should
have updated *info via PTRACE_SETSIGINFO. */
if (signr != info->si_signo) {
+ struct task_struct *tracer;
+
info->si_signo = signr;
info->si_errno = 0;
info->si_code = SI_USER;
- info->si_pid = task_pid_vnr(current->parent);
- info->si_uid = task_uid(current->parent);
+
+ rcu_read_lock();
+ tracer = current->parent;
+ if (task_ptrace(current)) {
+ info->si_pid = task_pid_vnr(tracer);
+ info->si_uid = task_uid(tracer);
+ } else {
+ info->si_pid = 0;
+ info->si_uid = 0;
+ }
+ rcu_read_unlock();
}
/* If the (new) signal is now blocked, requeue it. */
reply other threads:[~2009-05-30 22:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090530223824.GA30478@redhat.com \
--to=oleg@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox