linux-kernel - Re: [PATCH 03/15] tracing: Add a free on close control mechanism for buffer_size

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]

Message-ID: <1307966043.9218.63.camel@gandalf.stny.rr.com>
Date:	Mon, 13 Jun 2011 07:54:03 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Vaibhav Nagarnaik <vnagarnaik@...gle.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Michael Rubin <mrubin@...gle.com>,
	David Sharp <dhsharp@...gle.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH 03/15] tracing: Add a free on close control mechanism
 for buffer_size_kb

On Mon, 2011-06-13 at 13:49 +0200, Ingo Molnar wrote:

> > https://lkml.org/lkml/2011/3/17/366
> > 
> > I didn't really like adding another file to the debugfs system, and 
> > recommended the ioctl. It seemed like a nice "unix" fit. But if you 
> > want to go back to the Vaibhav's original method, which will stay 
> > in the frame of "human-parseable and scripted". We could do that.
> 
> Yes, i think so - the *only* point of the /debug/tracing/ muck is 
> that it's scriptable and human parseable. If Google wants to use it 
> for more than that then they should help us enhance the perf syscall 
> ABI for tracing ...

Hi Vaibhav,

Sorry for the spin around, but could you resubmit your original patch?

Thanks!

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