linux-kernel - Re: malloc() tracing in perf?

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:	Thu, 6 Aug 2009 09:47:36 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
cc:	"Frank Ch. Eigler" <fche@...hat.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Ingo Molnar <mingo@...e.hu>, acme <acme@...hat.com>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Eduard-Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
	roland <roland@...hat.com>,
	Christoph Hellwig <hch@...radead.org>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	linux-kernel@...r.kernel.org
Subject: Re: malloc() tracing in perf?


On Thu, 6 Aug 2009, Peter Zijlstra wrote:

> On Thu, 2009-08-06 at 07:55 -0400, Frank Ch. Eigler wrote:
> > Hi -
> > 
> > On Thu, Aug 06, 2009 at 01:28:14PM +0200, Peter Zijlstra wrote:
> > > [...]
> > > > That work is ongoing, and being discussed on utrace-devel@...hat.com,
> > > > since it is a prerequisite. 
> > > 
> > > Still hiding the discussion and the design never helped anybody.
> > 
> > I guess "hiding" is a matter of opinion.
> 
> Yeah in plain sight where nobody looks, really I thought the idea was to
> get utrace upstream, this means posting to linux-kernel. Going on LKML
> posts I'd say the utrace project was dead. Same goes for uprobe.
> 
> I've told this before and I'll say it again, post to LKML.

I second this. _Any_ kernel development that is new must be discussed on 
LKML. Sure, you can do the initial prototypes on a smaller mailing list, 
but once you have that prototype ready, it should go to LKML. This was the 
problem with Xen. The -rt patch was developed on LKML and even though 
there's a lot more to get in, a lot already has. The reason is that all 
development was done on the kernel mailing list.

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