linux-kernel - Re: [PATCH 3/3] utrace-based ftrace "process" engine, v2

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Mar 2009 12:25:04 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Theodore Tso <tytso@....edu>, oleg@...hat.com,
	adobriyan@...il.com, mingo@...e.hu, torvalds@...ux-foundation.org,
	fche@...hat.com, roland@...hat.com, rostedt@...dmis.org,
	utrace-devel@...hat.com, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, Christoph Hellwig <hch@...radead.org>,
	Jeff Dike <jdike@...toit.com>
Subject: Re: [PATCH 3/3] utrace-based ftrace "process" engine, v2

On Tue, Mar 31, 2009 at 11:17:42AM +0200, Peter Zijlstra wrote:
> > Could those who object to utrace please pipe up and summarise their
> > reasons?
> 
> Christoph used to have an opinion on this matter, so I've added him to
> the CC.

I've never objected utrace per see, quite contrary I think it's a useful
abstraction.  I did have objection over various implementation details
which should be sorted out now (have to take a look again to make sure).

I do have a really large objection of merging the current messy double
ptrace implementation.  If current utrace based ptrace isn't 100% ready
there's absolutely no point in merging it.  Other user would be even
better, e.g. the seccomp rewrite.

--
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/