linux-kernel - request to add trace off and trace on with events

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-next>] [day] [month] [year] [list]

Date:	Mon, 19 Apr 2010 16:04:04 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Tom Zanussi <tzanussi@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Chase Douglas <chase.douglas@...onical.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: request to add trace off and trace on with events

Hi Tom,

Could you add a way to do a call to tracing_on() or tracing_off() via
the filters. I would like to do something like:

echo 'if (pid == 1234) traceoff' > events/sched/sched_wakeup/filter

Where, if the sched_wakeup event is hit with pid == 1234 it will turn
tracing off.

I would also like to do just:

echo 'traceoff' > events/sched/sched_wakeup/filter

to disable tracing every time the event is hit.

Perhaps you can just add a call back where the kernel could register
something to be called if a command is used in the filter.

register_event_command("traceoff", trace_off_cb);

where the trace_off_cb is a function that is called by the event if the
traceoff command is hit. This would allow other commands to be added
later.

Would something like this be doable, I was looking at the code, and it
certain looks feasible, but it would take me longer to implement it than
it would you :-)

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/