From: Petr Tesarik <ptesarik@suse.cz>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Roland McGrath <roland@redhat.com>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [PATCH] Discard notification signals when a tracer exits
Date: Tue, 25 Mar 2008 15:37:58 +0100 [thread overview]
Message-ID: <1206455878.17227.11.camel@elijah.suse.cz> (raw)
In-Reply-To: <1206455513.17227.4.camel@elijah.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]
On Tue, 2008-03-25 at 15:31 +0100, Petr Tesarik wrote:
> When a tracer exits without detaching from the traced process, the
> tracee may be at a tracer notification stop and will thus interpret
> the value in task->exit_code (SIGTRAP | 0x80) as the signal to be
> delivered.
>
> This patch fixes the problem by clearing exit_code when detaching
> the traced process from a dying tracer.
>
> Signed-off-by: Petr Tesarik <ptesarik@suse.cz>
>
Oh, and here is a testing script for the first hunk. It fails on all
kernels I have tried. The second hunk can also be tested if you run
strace on the traced process instead of attaching to a running one, but
I didn't figure out how to get the PID of the traced process within a
script, so you'd have to trigger the bug manually.
> ---
> exit.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -642,8 +642,10 @@ reparent_thread(struct task_struct *p, s
> /*
> * If it was at a trace stop, turn it into
> * a normal stop since it's no longer being
> - * traced.
> + * traced. Cancel the notification signal,
> + * or the tracee may get a SIGTRAP.
> */
> + p->exit_code = 0;
> ptrace_untrace(p);
> }
> }
> @@ -713,6 +715,10 @@ static void forget_original_parent(struc
> p->real_parent = reaper;
> reparent_thread(p, father, 0);
> } else {
> + /* cancel the notification signal at a trace stop */
> + if (p->state == TASK_TRACED)
> + p->exit_code = 0;
> +
> /* reparent ptraced task to its real parent */
> __ptrace_unlink (p);
> if (p->exit_state == EXIT_ZOMBIE && p->exit_signal != -1 &&
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: test-trap.sh --]
[-- Type: application/x-shellscript, Size: 747 bytes --]
next prev parent reply other threads:[~2008-03-25 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 14:31 Petr Tesarik
2008-03-25 14:37 ` Petr Tesarik [this message]
2008-03-25 16:16 ` Oleg Nesterov
2008-03-25 16:33 ` Oleg Nesterov
2008-03-26 9:13 ` Petr Tesarik
2008-03-26 8:48 ` Petr Tesarik
2008-03-26 18:17 ` Oleg Nesterov
2008-03-27 8:06 ` Petr Tesarik
2008-03-27 13:44 ` Oleg Nesterov
2008-03-25 22:38 ` 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=1206455878.17227.11.camel@elijah.suse.cz \
--to=ptesarik@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--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
all inboxes | Powered by JetHome®