linux-kernel - Re: [PATCH] ptrace: arch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LFD.1.00.0803271957080.14670@woody.linux-foundation.org>
Date:	Thu, 27 Mar 2008 19:59:23 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Roland McGrath <roland@...hat.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH] ptrace: arch_ptrace cleanup



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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/