linux-kernel - Re: [PATCH 2/4] tracing: add event trace infrastructure

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: <alpine.DEB.2.00.0902250909330.12697@gandalf.stny.rr.com>
Date:	Wed, 25 Feb 2009 09:10:07 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Theodore Tso <tytso@....edu>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Pekka Paalanen <pq@....fi>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Jason Baron <jbaron@...hat.com>,
	Martin Bligh <mbligh@...gle.com>,
	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Jens Axboe <jens.axboe@...cle.com>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 2/4] tracing: add event trace infrastructure


On Wed, 25 Feb 2009, Theodore Tso wrote:

> On Tue, Feb 24, 2009 at 07:45:48PM -0800, Andrew Morton wrote:
> > echo sched_wakeup > /debug/tracing/set_event
> > echo sched_wakeup > /debug/tracing/clear_event
> > echo 1 > /debug/tracing/clear_all_events
> 
> >From a usability point of view, I'd prefer this as well.  It's only
> two extra files, but it means that filenames in /deb/tracing is
> self-documenting, which is a good thing.  Otherwise, it's really not
> obvious that "echo !event > /debug/tracing/set_event" will disable the
> event, and it's *especially* not obvious "echo > /debug/tracing/set_event"
> will disable all events.
> 
> It's also a tad bit too easy to typo "echo > /debug/tracing/set_event"
> by editing command history, and hitting return a bit too soon after
> clearing out the previous event name but before you manage to type the
> new event name.

OK, then I guess I can add a clear_event file. And to clear all events 
simply do:

 # cat set_event > clear_event

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