From: Oleg Nesterov <oleg@redhat.com>
To: Ales Novak <alnovak@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH] ptrace: clear TIF_SYSCALL_TRACE on ptrace detach
Date: Thu, 1 Sep 2016 18:46:13 +0200 [thread overview]
Message-ID: <20160901164613.GA13138@redhat.com> (raw)
In-Reply-To: <1472738076-14610-1-git-send-email-alnovak@suse.cz>
On 09/01, Ales Novak wrote:
>
> On ptrace_detach(), the TIF_SYSCALL_TRACE in thread->flags of the tracee
> is not cleared up. This results in the tracehook_report_syscall_* being
> called (though there's no longer a tracer listening to that) upon its
> further syscalls.
>
> Example scenario - attach "strace" to a running process and kill it (the
> strace) with SIGKILL. You'll see that the syscall trace hooks are still
> being called.
We do not really care, if the tracer dies the tracee can be in the
inconsistent state anyway.
> --- a/kernel/ptrace.c
> +++ b/kernel/ptrace.c
> @@ -85,6 +85,7 @@ void __ptrace_unlink(struct task_struct *child)
> task_clear_jobctl_pending(child, JOBCTL_TRAP_MASK);
> task_clear_jobctl_trapping(child);
>
> + clear_tsk_thread_flag(child, TIF_SYSCALL_TRACE);
OK, probably this change makes sense anyway, but then you should
remove another clear_tsk_thread_flag(TIF_SYSCALL_TRACE) in ptrace_detach?
And I'd suggest to move this clear_tsk_thread_flag() up, before
spin_lock(siglock). Otherwise it looks as if we should clear this flag
with ->siglock held.
Oleg.
next prev parent reply other threads:[~2016-09-01 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 13:54 [PATCH] ptrace: clear TIF_SYSCALL_TRACE on ptrace detach Ales Novak
2016-09-01 16:46 ` Oleg Nesterov [this message]
2016-09-01 19:50 ` Ales Novak
2016-09-01 19:51 ` Ales Novak
2016-09-02 12:25 ` Oleg Nesterov
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=20160901164613.GA13138@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alnovak@suse.cz \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).