linux-kernel - Re: [RFC][PATCH] tracing: Warn and notify if tracepoints are not loaded due to module taint

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Feb 2014 19:49:26 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [RFC][PATCH] tracing: Warn and notify if tracepoints are not
 loaded due to module taint

On Wed, 26 Feb 2014 00:39:01 +0000 (UTC)
Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote:

> ----- Original Message -----
> > From: "Steven Rostedt" <rostedt@...dmis.org>
> > To: "LKML" <linux-kernel@...r.kernel.org>
> > Cc: "Ingo Molnar" <mingo@...nel.org>, "Mathieu Desnoyers" <mathieu.desnoyers@...icios.com>, "Rusty Russell"
> > <rusty@...tcorp.com.au>, "Frederic Weisbecker" <fweisbec@...il.com>, "Andrew Morton" <akpm@...ux-foundation.org>,
> > "Peter Zijlstra" <peterz@...radead.org>
> > Sent: Tuesday, February 25, 2014 7:15:05 PM
> > Subject: [RFC][PATCH] tracing: Warn and notify if tracepoints are not loaded due to module taint
> > 
> > [ Posting this as an RFC, but I plan on pushing it as soon as I finish
> > testing it ]
> > 
> > If a module is loaded that is tainted with anything but OOT or CRAP, then
> > it will not create the traceoint infrastructure for the module. There should
> 
> traceoint -> tracepoint

Oops, thanks.

> 
> > be a big warning when this happens instead of exiting silently.
> > 
> > Fixes: 97e1c18e8d17 "tracing: Kernel Tracepoints"
> > Cc: stable@...r.kernel.org
> > Cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
> > ---
> >  kernel/tracepoint.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
> > index 29f2654..413bc06 100644
> > --- a/kernel/tracepoint.c
> > +++ b/kernel/tracepoint.c
> > @@ -641,7 +641,8 @@ 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 (WARN_ONCE(mod->taints & ~((1 << TAINT_OOT_MODULE) | (1 << TAINT_CRAP)),
> > +		      "Module is tainted, disabling tracepoints"))
> 
> Perhaps ever clearer with:
> 
>    "Module \"%s\" is tainted, disabling tracepoints", mod->name
> 
> ?

I originally had that with a simple WARN() instead of WARN_ONCE(), but
if you have that config which makes all modules not have sigs correct,
it spits out tens of these warnings and can cause more panic in users
than it deserves. I then switched it to WARN_ONCE(), and then thought,
that if it does it only once for the first module, it wont print the
warning again for the other affected modules. That means it may confuse
the user if they see a module had that warning, but the module they are
trying to trace isn't working either.

I then figured it would be good to remove the module name and just
state a general "Module is tainted, disabling tracepoints" and if the
user notices that the module isn't working, and then looks at their
dmesg, they'll see this message and just assume it was the module that
wasn't working.

Make sense?

-- Steve


> 
> Other than that, looks good to me!
> 

--
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/