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
| ||
|
Date: Wed, 12 Mar 2014 20:49:07 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com> Cc: "Frank Ch. Eigler" <fche@...hat.com>, linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>, Frederic Weisbecker <fweisbec@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, Johannes Berg <johannes.berg@...el.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Peter Zijlstra <peterz@...radead.org>, Thomas Gleixner <tglx@...utronix.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, lttng-dev <lttng-dev@...ts.lttng.org>, Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <andi@...stfloor.org> Subject: Re: [for-next][PATCH 08/20] tracing: Warn if a tracepoint is not set via debugfs On Wed, 12 Mar 2014 19:51:01 +0000 (UTC) Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote: > This only leaves tracepoints in header files and the impact of LTO as > requirements for having tracepoint callsites with the same name across > modules. The only thing that needs to be unique is the struct tracepoint __tracepoint_##name. There should not be any duplicates of those. I can't see how the LTO would duplicate a data structure without screwing everything (not just tracepoints) up. We can still have more than one trace_##name() called, as that is handled by the static key. Note, I'm scrambling to get ready for my trip tomorrow. Thus, I'm not as much at the computer. I may work on some patches in my 6 hour layover though. -- 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/
Powered by blists - more mailing lists