| 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
| ||
|
Message-ID: <20150421061034.GA9253@infradead.org> Date: Mon, 20 Apr 2015 23:10:34 -0700 From: Christoph Hellwig <hch@...radead.org> To: Ron Rechenmacher <ron@...l.gov> Cc: linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org> Subject: Re: [PATCH] tracing: Export key trace event symbols On Mon, Apr 20, 2015 at 04:38:11PM -0500, Ron Rechenmacher wrote: > If symbols are not exported, modules can no longer register additional > (module specified) tracepoints like they use to be able to (i.e linux-3.15.x). > Somewhere on or about commit de7b2973903c6cc50b31ee5682a69b2219b9919d > (Author: Mathieu Desnoyers <mathieu.desnoyers@...icios.com> > Date: Tue Apr 8 17:26:21 2014 -0400 > tracepoint: Use struct pointer instead of name hash for reg/unreg tracepoints) > modules which attempted to register additional tracing functions would > get "Unknown symbol" errors. For example: "... Unknown symbol > __tracepoint_sched_switch (err 0)" > Symbols can be exported using the kernel's EXPORT_TRACEPOINT_SYMBOL_GPL macro > to allow modules to once again register their own tracing functions (for at > least some key points in the kernel as provided by this patch). Which (in-tree) module fails with this? I don't think anyone should actually register a symbol. -- 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