From: Oleg Nesterov <oleg@redhat.com>
To: Keno Fischer <keno@juliacomputing.com>
Cc: roland@hack.frob.com, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>
Subject: Re: ptrace group stop signal number not reset before PTRACE_INTERRUPT is delivered?
Date: Thu, 18 Aug 2016 18:23:11 +0200 [thread overview]
Message-ID: <20160818162311.GA27883@redhat.com> (raw)
In-Reply-To: <20160818153806.GA25492@redhat.com>
Damn, forgot to mention...
On 08/18, Oleg Nesterov wrote:
>
> Damn. I'll try to think more, but I simply can't decide what do we
> actually want in this case.
Yes, but at least
> Further, the current behavior seems to make it
> very hard (impossible?) to reliably tell a true group-stop from a
> PTRACE_INTERRUPT generated one.
is not true or I misunderstood... PTRACE_INTERRUPT doesn't lead to
group-stop, it stops the tracee individually.
And you if you get PTRACE_EVENT_STOP and WSTOPSIG() == SIGTTIN after
PTRACE_INTERRUPT, you know that the tracee did not report the "new"
SIGTTIN.
Or I missed your point?
Oleg.
next prev parent reply other threads:[~2016-08-19 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 3:52 ptrace group stop signal number not reset before PTRACE_INTERRUPT is delivered? Keno Fischer
2016-08-18 14:37 ` Oleg Nesterov
2016-08-18 15:38 ` Oleg Nesterov
2016-08-18 16:23 ` Oleg Nesterov [this message]
2016-08-18 17:37 ` Keno Fischer
2016-08-23 15:34 ` Oleg Nesterov
2016-09-13 21:57 ` Keno Fischer
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=20160818162311.GA27883@redhat.com \
--to=oleg@redhat.com \
--cc=keno@juliacomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@hack.frob.com \
--cc=tj@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).