Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757444AbYC1C74 (ORCPT ); Thu, 27 Mar 2008 22:59:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755456AbYC1C7q (ORCPT ); Thu, 27 Mar 2008 22:59:46 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:44563 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755073AbYC1C7p (ORCPT ); Thu, 27 Mar 2008 22:59:45 -0400 Date: Thu, 27 Mar 2008 19:59:23 -0700 (PDT) From: Linus Torvalds To: Roland McGrath cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org Subject: Re: [PATCH] ptrace: arch_ptrace cleanup In-Reply-To: <20080328023155.71B6626FA1C@magilla.localdomain> Message-ID: References: <20080327230623.969FF26FA1C@magilla.localdomain> <20080328023155.71B6626FA1C@magilla.localdomain> User-Agent: Alpine 1.00 (LFD 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1067 Lines: 25 On Thu, 27 Mar 2008, Roland McGrath wrote: > > One of these days I will post substantial core ptrace changes. I don't > know what these are yet, but I know it's likely they will need to change > what's passed between sys_ptrace and ptrace_request/ptrace_resume. We > can expect that there will be churn in that code while we hash out how > it should be. Doing this arch patch first means that none of that later > churn will involve changing arch_ptrace back and forth while the > non-arch code gets settled. Why would that happen _anyway_? I'm very much against ugly interfaces that don't seem to fix anything. Especially if you don't even know that it's needed. I'm not doing to apply something that just makes code uglier before I actually see the thing that it helps with. Right now it only hurts. Linus -- 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/