linux-kernel - Re: [PATCH] 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:	Thu, 2 Apr 2009 03:58:30 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Tom Zanussi <tzanussi@...il.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing/filters: add run-time field descriptions to
	TRACE_EVENT_FORMAT events


* Steven Rostedt <rostedt@...dmis.org> wrote:

> Now what I could do, is to add a cmpxchg. If there's no data after 
> the data that we want to discard, then we discard it. Note, this 
> can only happen before the commit is made.
> 
> I'll see if I can implement that.

Great!

I dont think the IRQ race is a common one even with a lot of IRQs, 
so as long as the common case is fine and we let a few holes slip 
through it should be fine.

[ If the IRQ race window is wide then that's a sign of us having too 
  much tracing overhead ;-) ]

	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/