From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: [RFA][PATCH 4/4] tracing: Do not add event files for modules that fail tracepoints
Date: Wed, 26 Feb 2014 14:01:44 -0500 [thread overview]
Message-ID: <20140226190644.873393336@goodmis.org> (raw)
In-Reply-To: 20140226190140.590029589@goodmis.org
[-- Attachment #1: 0004-tracing-Do-not-add-event-files-for-modules-that-fail.patch --]
[-- Type: text/plain, Size: 2667 bytes --]
From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
If a module fails to add its tracepoints due to module tainting, do not
create the module event infrastructure in the debugfs directory. As the events
will not work and worse yet, they will silently fail, making the user wonder
why the events they enable do not display anything.
Having a warning on module load and the events not visible to the users
will make the cause of the problem much clearer.
Fixes: 6d723736e472 "tracing/events: add support for modules to TRACE_EVENT"
Cc: stable@vger.kernel.org # 2.6.31+
Cc: Rusty Russell <rusty@rustcorp.com.au>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
include/linux/tracepoint.h | 7 +++++++
kernel/trace/trace_events.c | 4 ++++
kernel/tracepoint.c | 2 +-
3 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/include/linux/tracepoint.h b/include/linux/tracepoint.h
index accc497..3cb2842 100644
--- a/include/linux/tracepoint.h
+++ b/include/linux/tracepoint.h
@@ -16,6 +16,7 @@
#include <linux/errno.h>
#include <linux/types.h>
+#include <linux/module.h>
#include <linux/rcupdate.h>
#include <linux/static_key.h>
@@ -60,6 +61,12 @@ struct tp_module {
unsigned int num_tracepoints;
struct tracepoint * const *tracepoints_ptrs;
};
+static inline bool trace_module_has_bad_taint(struct module *mod)
+{
+ return mod->taints & ~((1 << TAINT_OOT_MODULE) | (1 << TAINT_CRAP));
+}
+#else
+#define trace_module_has_bad_taint(mod) ({false;})
#endif /* CONFIG_MODULES */
struct tracepoint_iter {
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index e71ffd4..b2fee73 100644
--- a/kernel/trace/trace_events.c
+++ b/kernel/trace/trace_events.c
@@ -1777,6 +1777,10 @@ static void trace_module_add_events(struct module *mod)
{
struct ftrace_event_call **call, **start, **end;
+ /* Don't add infrastructure for mods without tracepoints */
+ if (trace_module_has_bad_taint(mod))
+ return;
+
start = mod->trace_events;
end = mod->trace_events + mod->num_trace_events;
diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
index 8a5d5e95..f74e953 100644
--- a/kernel/tracepoint.c
+++ b/kernel/tracepoint.c
@@ -644,7 +644,7 @@ static int tracepoint_module_coming(struct module *mod)
* module headers (for forced load), to make sure we don't cause a crash.
* Staging and out-of-tree GPL modules are fine.
*/
- if (mod->taints & ~((1 << TAINT_OOT_MODULE) | (1 << TAINT_CRAP))) {
+ if (trace_module_has_bad_taint(mod)) {
pr_err("Module '%s' is tainted, disabling tracepoints\n",
mod->name);
return 0;
--
1.8.5.3
next prev parent reply other threads:[~2014-02-26 19:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 19:01 [RFA][PATCH 0/4] tracing: Request for acks on fixing tracepoint code Steven Rostedt
2014-02-26 19:01 ` [RFA][PATCH 1/4] tracing: Fix event header writeback.h to include tracepoint.h Steven Rostedt
2014-02-26 19:01 ` [RFA][PATCH 2/4] tracing: Fix event header migrate.h " Steven Rostedt
2014-02-28 11:22 ` Mel Gorman
2014-02-26 19:01 ` [RFA][PATCH 3/4] tracing/module: Remove include of tracepoint.h from module.h Steven Rostedt
2014-02-27 3:13 ` Steven Rostedt
2014-03-17 2:34 ` Rusty Russell
2014-03-17 6:42 ` Steven Rostedt
2014-02-26 19:01 ` Steven Rostedt [this message]
2014-02-26 21:36 ` [RFA][PATCH 0/4] tracing: Request for acks on fixing tracepoint code Mathieu Desnoyers
2014-02-27 1:38 ` Steven Rostedt
2014-02-27 2:21 ` Mathieu Desnoyers
2014-02-27 2:43 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140226190644.873393336@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox