| 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: Thu, 13 Mar 2014 14:17:53 -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> Subject: Re: [RFC PATCH v2] Tracepoint: register/unregister struct tracepoint On Thu, 2014-03-13 at 16:54 +0000, Mathieu Desnoyers wrote: > The other use-case is if the tracer has a module coming/going notifier > tracking the module's tracepoint callsites. The going notifier should > be run before the tracepoint.c going notifier. A notifier with negative > priority should have this effect, since the tracepoint.c notifier has > priority 0. > The tracepoint should change to have two different notifiers that represent one for coming and one for going (as ftrace does). The coming one should have a priority of 0 (or INT_MIN (all other notifiers dependent on this should have > 0) The going notifier should have a INT_MAX to run after all other tracepoint notifiers. (see kernel/trace/ftrace.c ftrace_module_enter_nb and ftrace_module_exit_nb) -- 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