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: Re: [RFC PATCH 7/X] ptrace: mv task->parent ptrace_task->pt_tracer
Date: Thu, 28 May 2009 04:54:07 +0200 [thread overview]
Message-ID: <20090528025407.GA22182@redhat.com> (raw)
In-Reply-To: <20090528003256.86E4EFC2BD@magilla.sf.frob.com>
On 05/27, Roland McGrath wrote:
>
> > OK, lets do this change later ;)
>
> Agreed.
Damn. OTOH, it is so ugly to cache pid/uid for the very unlikely case.
Roland, will you agree with the patch below?
If yes, I'd like to send it separately.
Oleg.
-------------------------------------------------------------------
[PATCH -mm] ptrace: ptrace_signal: fix the usage of ->parent
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.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
--- PTRACE/kernel/signal.c~PTRACE_SIGNAL 2009-05-28 04:12:02.000000000 +0200
+++ PTRACE/kernel/signal.c 2009-05-28 04:14:38.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. */
next prev parent reply other threads:[~2009-05-28 2:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 0:00 [RFC PATCH 7/X] ptrace: mv task->parent ptrace_task->pt_tracer Oleg Nesterov
2009-05-25 21:59 ` Oleg Nesterov
2009-05-25 22:39 ` [RFC PATCH 8/X] ptrace: introduce ptrace_tracer() helper Oleg Nesterov
2009-05-27 2:45 ` Roland McGrath
2009-05-27 21:45 ` Oleg Nesterov
2009-05-27 22:24 ` Roland McGrath
2009-05-27 2:11 ` [RFC PATCH 7/X] ptrace: mv task->parent ptrace_task->pt_tracer Roland McGrath
2009-05-27 22:41 ` Oleg Nesterov
2009-05-27 23:05 ` ptrace && task->exit_code Oleg Nesterov
2009-05-27 23:21 ` Roland McGrath
2009-05-29 19:06 ` Oleg Nesterov
2009-06-01 2:16 ` Roland McGrath
2009-05-27 23:07 ` [RFC PATCH 7/X] ptrace: mv task->parent ptrace_task->pt_tracer Roland McGrath
2009-05-27 23:59 ` Oleg Nesterov
2009-05-28 0:32 ` Roland McGrath
2009-05-28 2:54 ` Oleg Nesterov [this message]
2009-05-28 3:19 ` Roland McGrath
2009-05-28 3:35 ` Oleg Nesterov
2009-05-28 19:28 ` Roland McGrath
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=20090528025407.GA22182@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