From: Tejun Heo <tj@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH ptrace] ptrace: use GROUP_STOP_TRAPPING for PTRACE_DETACH too
Date: Sun, 8 May 2011 16:44:24 +0200 [thread overview]
Message-ID: <20110508144424.GB29783@htj.dyndns.org> (raw)
Currently GROUP_STOP_TRAPPING is used only for PTRACE_ATTACH to hide
STOPPED -> RUNNING -> TRACED transition; however, DETACH involves
similar transition in the reverse direction, which can be visible to
the next ptracer if it attaches before the transition is complete.
This patch makes DETACH also use TRAPPING and ptrace_attach() always
wait if TRAPPING is set to hide the transition.
Test program follows.
int main(int argc, char **argv)
{
pid_t tracee;
siginfo_t si = {};
int i, nr_wait_fails = 0, nr_ptrace_fails = 0;
tracee = fork();
if (!tracee)
while (1)
pause();
kill(tracee, SIGSTOP);
waitid(P_PID, tracee, NULL, WSTOPPED | WNOWAIT);
for (i = 0; i < 100000; i++) {
ptrace(PTRACE_ATTACH, tracee, NULL, NULL);
waitid(P_PID, tracee, &si, WSTOPPED | WNOHANG);
if (!si.si_pid)
nr_wait_fails++;
if (ptrace(PTRACE_DETACH, tracee, NULL, NULL)) {
nr_ptrace_fails++;
waitid(P_PID, tracee, NULL, WSTOPPED);
ptrace(PTRACE_DETACH, tracee, NULL, NULL);
}
}
printf("wait/ptrace failed %d/%d times out of %d tries\n",
nr_wait_fails, nr_ptrace_fails, i);
return 0;
}
Before the patch, transition from DETACH causes sporadic failures on
waitid(2) and ptrace(2) calls after re-attaching.
# ./test-trapping-race
wait/ptrace failed 453/449 times out of 100000 tries
After, PTRACE_ATTACH waits for the previous transitions to complete
too and they don't fail.
# ./test-trapping-race-simple
wait/ptrace failed 0/0 times out of 100000 tries
Signed-off-by: Tejun Heo <tj@kernel.org>
---
kernel/ptrace.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
Index: work/kernel/ptrace.c
===================================================================
--- work.orig/kernel/ptrace.c
+++ work/kernel/ptrace.c
@@ -77,12 +77,15 @@ void __ptrace_unlink(struct task_struct
/*
* Reinstate GROUP_STOP_PENDING if group stop is in effect and
- * @child isn't dead.
+ * @child isn't dead. This will trigger TRACED -> RUNNING ->
+ * STOPPED transition. As this transition can affect the next
+ * ptracer if it attaches before the transition completes, set
+ * TRAPPING too. Read comment in ptrace_attach() for more details.
*/
if (!(child->flags & PF_EXITING) &&
(child->signal->flags & SIGNAL_STOP_STOPPED ||
child->signal->group_stop_count))
- child->group_stop |= GROUP_STOP_PENDING;
+ child->group_stop |= GROUP_STOP_PENDING | GROUP_STOP_TRAPPING;
/*
* If transition to TASK_STOPPED is pending or in TASK_TRACED, kick
@@ -183,7 +186,6 @@ bool ptrace_may_access(struct task_struc
static int ptrace_attach(struct task_struct *task)
{
- bool wait_trap = false;
int retval;
audit_ptrace(task);
@@ -245,7 +247,6 @@ static int ptrace_attach(struct task_str
if (task_is_stopped(task)) {
task->group_stop |= GROUP_STOP_PENDING | GROUP_STOP_TRAPPING;
signal_wake_up(task, 1);
- wait_trap = true;
}
spin_unlock(&task->sighand->siglock);
@@ -256,9 +257,8 @@ unlock_tasklist:
unlock_creds:
mutex_unlock(&task->signal->cred_guard_mutex);
out:
- if (wait_trap)
- wait_event(current->signal->wait_chldexit,
- !(task->group_stop & GROUP_STOP_TRAPPING));
+ wait_event(current->signal->wait_chldexit,
+ !(task->group_stop & GROUP_STOP_TRAPPING));
return retval;
}
next reply other threads:[~2011-05-08 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 14:44 Tejun Heo [this message]
2011-05-08 16:07 ` Oleg Nesterov
2011-05-09 8:37 ` Tejun Heo
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=20110508144424.GB29783@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®