mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Roland McGrath <roland@redhat.com>,
	Daniel Jacobowitz <dan@debian.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: More waitpid issues with CLONE_DETACHED/CLONE_THREAD
Date: Mon, 2 Feb 2004 03:20:23 +0100	[thread overview]
Message-ID: <20040202032023.A28264@pclin040.win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0402011653230.2229@home.osdl.org>; from torvalds@osdl.org on Sun, Feb 01, 2004 at 04:55:11PM -0800

On Sun, Feb 01, 2004 at 04:55:11PM -0800, Linus Torvalds wrote:

> On Sun, 1 Feb 2004, Roland McGrath wrote:

> > I haven't really looked into the problem with Dan's test case yet (didn't
> > seem to reproduce, but I haven't tried a current and cruft-free kernel yet).  
> > But I don't see any problem with the implementation of PTRACE_KILL.
> 
> Hmm.. For me, Dan's program (with "-DBUG -DNOTHREAD") results in a 
> sleeping parent, and both children are likewise just sleeping. Despite the 
> fact that the parent just did the PTRACE_KILL on child2.
> 
> I didn't trace it through the kernel, it just looked like PTRACE_KILL 
> didn't do anything.

I agree with both of you.

So, I think what happens is that PTRACE_KILL immediately after the PTRACE_CONT
works because there is no schedule in between, so the effect of PTRACE_KILL
is still seen by the (grand)child.
Once the grandchild has returned it has become immune for PTRACE_KILL.
Maybe there is no bug.

Andries

  reply	other threads:[~2004-02-02  2:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01  3:25 Daniel Jacobowitz
2004-02-01  4:38 ` Linus Torvalds
2004-02-01  4:43   ` Daniel Jacobowitz
2004-02-01  5:12     ` Daniel Jacobowitz
2004-02-01 21:41       ` Linus Torvalds
2004-02-01 22:25         ` Roland McGrath
2004-02-02  0:55           ` Linus Torvalds
2004-02-02  2:20             ` Andries Brouwer [this message]
2004-02-02  2:30               ` Linus Torvalds
2004-02-02  0:52         ` Daniel Jacobowitz
2004-02-02  2:41           ` Davide Libenzi
2004-02-02  2:55             ` Davide Libenzi
2004-02-04 14:22               ` fs/eventpoll : reduce sizeof(struct epitem) dada1
2004-02-05  4:23                 ` Davide Libenzi
2004-02-01  5:12     ` More waitpid issues with CLONE_DETACHED/CLONE_THREAD Linus Torvalds
2004-02-01  5:14       ` Daniel Jacobowitz
2004-02-01  5:42         ` Roland McGrath
2004-02-01  5:46           ` Daniel Jacobowitz

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=20040202032023.A28264@pclin040.win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=dan@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=roland@redhat.com \
    --cc=torvalds@osdl.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®