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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: More waitpid issues with CLONE_DETACHED/CLONE_THREADAndries Brouwer
- Re: More waitpid issues with CLONE_DETACHED/CLONE_THREADRoland McGrath
- Prev by Date: Re: 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs
- Next by Date: Re: [CRYPTO]: Miscompiling sha256.c by gcc 3.2.3 and arch pentium3,4
- Previous by thread: Re: More waitpid issues with CLONE_DETACHED/CLONE_THREAD
- Next by thread: Re: More waitpid issues with CLONE_DETACHED/CLONE_THREAD
- Indexes:[Main][Thread]