| 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
| ||
|
Date: Tue, 22 Dec 2009 13:58:09 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Oleg Nesterov <oleg@...hat.com> Cc: Alexey Dobriyan <adobriyan@...il.com>, Andi Kleen <andi@...stfloor.org>, Ananth Mavinakayanahalli <ananth@...ibm.com>, Christoph Hellwig <hch@...radead.org>, "Frank Ch. Eigler" <fche@...hat.com>, Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>, Roland McGrath <roland@...hat.com>, linux-kernel@...r.kernel.org, utrace-devel@...hat.com Subject: Re: [PATCH 0/7] utrace/ptrace On Fri, 18 Dec 2009 02:11:16 +0100 Oleg Nesterov <oleg@...hat.com> wrote: > Hello. > > This is the new iteration of Roland's utrace patch, this time > with "rewrite-ptrace-via-utrace" + cleanups in utrace core. > So... should we merge this? I'll confess that I've rather forgotten why we might want this. > It allows for multiple separate tracing engines to work > in parallel without interfering with each other. Higher-level tracing > facilities can be implemented as loadable kernel modules using this layer. That's a bit brief. Do you have a nicer sales brochure? What are these "separate tracing engines" and what is their merge status and why would we want any of them, for what purpose? etc. IOW: give us a reason! -- 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