DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=bZe/yDx9Kr0MOuPVFQHTFJsc7/54aPwt02WhuF4RTCshsXiW1lFQ4DOROo5TN8a2Ag
         0E5C9IeZ8SD6254j2C4AgghrYVa6SDfRmbVajMUgVe4LA3VEsSezeMu02jyGr8egO7lC
         LhNXK6Hz1Ev+eRQXNJr7utBlFhSWCPlzaybCA=
MIME-Version: 1.0
In-Reply-To: <20100202185907.GE3630@lst.de>
References: <20100202185755.GA3630@lst.de> <20100202185907.GE3630@lst.de>
From: Mike Frysinger <vapier.adi@gmail.com>
Date: Tue, 2 Feb 2010 15:29:38 -0500
Message-ID: <8bd0f97a1002021229x1c84d13flcc95102b7723468c@mail.gmail.com>
Subject: Re: [PATCH 5/14] blackfin: use generic ptrace_resume code
To: Christoph Hellwig <hch@lst.de>
Cc: roland@redhat.com, oleg@redhat.com, akpm@linux-foundation.org,
       vapier@gentoo.org, linux-kernel@vger.kernel.org,
       linux-arch@vger.kernel.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1007
Lines: 21

On Tue, Feb 2, 2010 at 13:59, Christoph Hellwig wrote:
> Use the generic ptrace_resume code for PTRACE_SYSCALL, PTRACE_CONT,
> PTRACE_KILL and PTRACE_SINGLESTEP.  This implies defining
> arch_has_single_step in <asm/ptrace.h> and implementing the
> user_enable_single_step and user_disable_single_step functions, which
> also causes the breakpoint information to be cleared on fork, which
> could be considered a bug fix.
>
> Also the TIF_SYSCALL_TRACE thread flag is now cleared on PTRACE_KILL
> which it previously wasn't which is consistent with all architectures
> using the modern ptrace code.

i have local code in the Blackfin tree that does part of this patch
(and has been tested), so i'll split this patch apart and merge into
my tree.  thanks!
-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/