All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: oleg@redhat.com, roland@redhat.com, linux-kernel@vger.kernel.org,
	rjw@sisk.pl
Subject: Re: [PATCH 1/4] signal: fix SIGCONT notification code
Date: Wed, 12 Jan 2011 21:41:36 +0100	[thread overview]
Message-ID: <20110112204136.GB13830@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <1293016398-18001-2-git-send-email-tj@kernel.org>

On Wed, 22 Dec 2010 12:13:15 +0100, Tejun Heo wrote:
> If SIGCONT is received while the child process is stopped, the code should
> be CLD_CONTINUED.  If SIGCONT is recieved while the child process is in the
> process of being stopped, it should be CLD_STOPPED.

If a process does
	kill (PID, SIGSTOP);
	<varying delay, possibly even from a different process>
	kill (PID, SIGCONT);

does it mean the PID's parent may get different waitid() results?
Or even that PID will finally remain still `T (stopped)'?

I do not see it has any userland impact, the
PTRACE_ATTACH-to-T(stopped)-process is already racy for different reasons.


Thanks,
Jan

  reply	other threads:[~2011-01-12 20:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 11:13 [PATCHSET] ptrace,signal: cleanups and fixes Tejun Heo
2010-12-22 11:13 ` [PATCH 1/4] signal: fix SIGCONT notification code Tejun Heo
2011-01-12 20:41   ` Jan Kratochvil [this message]
2011-01-13 11:27     ` Tejun Heo
2011-01-13 14:40     ` Oleg Nesterov
2010-12-22 11:13 ` [PATCH 2/4] ptrace: remove the extra wake_up_process() from ptrace_detach() Tejun Heo
2011-01-17 22:13   ` Roland McGrath
2011-01-27 13:34     ` Tejun Heo
2011-01-28  7:02       ` Roland McGrath
2011-01-28 10:59         ` Tejun Heo
2010-12-22 11:13 ` [PATCH 3/4] signal: remove superflous try_to_freeze() loop in do_signal_stop() Tejun Heo
2011-01-17 22:10   ` Roland McGrath
2010-12-22 11:13 ` [PATCH 4/4] ptrace: kill tracehook_notify_jctl() Tejun Heo
2011-01-17 22:14   ` 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=20110112204136.GB13830@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=roland@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.