linux-kernel - Re: [PATCH v2] tracing/filters: add run-time field descriptions to TRACE_EVENT

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

Date:	Wed, 1 Apr 2009 14:21:22 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Tom Zanussi <tzanussi@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>, fweisbec@...il.com
Subject: Re: [PATCH v2] tracing/filters: add run-time field descriptions to
	TRACE_EVENT_FORMAT events


* Tom Zanussi <tzanussi@...il.com> wrote:

> The other is that for the really high-volume tracers e.g. the 
> function tracer, the volume of filtered events can be so high that 
> it pushes the unfiltered events out of the ring buffer before they 
> can be read so e.g. cat'ing the trace file repeatedly shows either 
> no output, or once in awhile some output but that isn't there the 
> next time you read the trace, which isn't what you normally expect 
> when reading the trace file. If you read from the trace_pipe file 
> though, you can catch them before they disappear.

yeah - this artifact of the ringbuffer needs to be fixed too. Steve, 
what's the plans on that?

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