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: <20240725095307.3067329f@gandalf.local.home>
Date: Thu, 25 Jul 2024 09:53:07 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, Masami Hiramatsu <mhiramat@...nel.org>,
 Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [PATCH] tracing: remove tracing_is_on export

On Thu, 25 Jul 2024 15:35:00 +0200
Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:

> Generally, we don't allow symbols that are not actually being used in
> the kernel tree?  tracing_is_on() is a "code flow" type of thing, where
> code can operate differently if it is enabled or not.
> 
> And I would argue that tracing_on() and tracing_off() should also not be
> allowed to be in a module, why would you want that?  Just enable/disable
> it from userspace when doing your testing, IF you have permission to do
> so.

tracing_off() is key to development, and one that I would argue very much
against removing. The other two are more just for "completeness".

It usually is used by adding a bunch of trace_printk(), and then:

	if (condition) {
		trace_printk("Condition hit!\n");
		tracing_off();
	}

And then you run your kernel until you noticed that something weird
happened. Then look at the trace file, and it will have all the events that
happened up to the anomaly condition, and you don't have to worry about the
ring buffer overflowing and losing your data.

This workflow is used by many developers.

-- Steve



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ