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:	Wed, 25 Nov 2009 16:50:18 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Oleg Nesterov <oleg@...hat.com>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Ananth Mavinakayanahalli <ananth@...ibm.com>,
	Christoph Hellwig <hch@...radead.org>,
	"Frank Ch. Eigler" <fche@...hat.com>, Ingo@...stfloor.org,
	"Molnar <mingo"@firstfloor.org, utrace-devel@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC,PATCH 14/14] utrace core

On Tue, Nov 24, 2009 at 09:32:27PM +0100, Andi Kleen wrote:
> Oleg Nesterov <oleg@...hat.com> writes:
> 
> > From: Roland McGrath <roland@...hat.com>
> >
> > This adds the utrace facility, a new modular interface in the kernel
> > for implementing user thread tracing and debugging.  This fits on top
> > of the tracehook_* layer, so the new code is well-isolated.
> 
> Could we just drop the tracehook layer if this finally merged
> and call the low level functions directly?
> 
> It might have been reasonably early on when it was still out of tree,
> but longer term when it's integrated having strange opaque hooks
> like that just makes the coder harder to read and maintain.

I agree that linux/tracehook.h as a separate layer is pretty annoying,
but a lot of the helper actually are quite useful.  I'd suggest to throw
a patch ontop of the series to rename all the useful macros to utrace_
and move them into utrace.h and just remove those that are really
trivial wrappers.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ