DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=mBp+iMzC6htzj+/AIvcdw8AZl8HFkrzecpnbynLUrSBlFumK+J5rHEyGCDbGav6eif
         zyEoaaeNKa2iCiUObNDMnoHPu/Aauhk6Vrpw458/AkThsuAxVXP0HJEscTBCx9KfWgLD
         Vi87aOKgLPjpv9l9vH2zLXYPYtpjLmzQAPJEU=
Message-ID: <8bd0f97a0810271038g4f0b7326r68c7e88841d0e6f9@mail.gmail.com>
Date: Mon, 27 Oct 2008 13:38:16 -0400
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Jan Kratochvil" <jan.kratochvil@redhat.com>
Subject: Re: inconsistent behavior with ptrace(TRACEME) and fork/exec
Cc: "Mike Frysinger" <vapier@gentoo.org>, linux-kernel@vger.kernel.org
In-Reply-To: <20081027145648.GA15791@host0.dyn.jankratochvil.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20081027145648.GA15791@host0.dyn.jankratochvil.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1365
Lines: 28

On Mon, Oct 27, 2008 at 10:56, Jan Kratochvil wrote:
> On Wed, 19 Jul 2006 21:18:29 +0200, Mike Frysinger wrote:
>> my understanding is that if a parent forks and the child does
>> a ptrace(TRACEME) right before doing an exec(), the kernel should always
>> halt it and wait indefinitely for the parent to start ptracing it.
>
> Yes, just the parent must process the event (signal).  In your testcase the
> parent finished before the signal could be delivered.  If the tracer exits the
> tracee's tracing is finished and it continues freely.

no signal should have been generated.  the child should have gone
straight to the exec and waited for the parent to process it.

>> unfortunately, this behavior seems to be unreliable.
>
> Fixed the races in your code and I do not see there any problem, do you?
> The ptrace problems/testsuite is being maintained at:
>  http://sourceware.org/systemtap/wiki/utrace/tests

there is no race condition ... it's using vfork here remember ?  it is
impossible for the parent to have executed anything after the vfork()
before the child made it into the exec() and gone to sleep
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/