From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265536AbUBBAzZ (ORCPT ); Sun, 1 Feb 2004 19:55:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265538AbUBBAzZ (ORCPT ); Sun, 1 Feb 2004 19:55:25 -0500 Received: from fw.osdl.org ([65.172.181.6]:53208 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S265536AbUBBAzU (ORCPT ); Sun, 1 Feb 2004 19:55:20 -0500 Date: Sun, 1 Feb 2004 16:55:11 -0800 (PST) From: Linus Torvalds To: Roland McGrath cc: Daniel Jacobowitz , Kernel Mailing List , Ingo Molnar Subject: Re: More waitpid issues with CLONE_DETACHED/CLONE_THREAD In-Reply-To: <200402012225.i11MPEN1009925@magilla.sf.frob.com> Message-ID: References: <200402012225.i11MPEN1009925@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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. Linus