linux-kernel - Re: [PATCH 0/5] [GIT PULL] updates for tip

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:	Thu, 16 Apr 2009 09:52:10 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/5] [GIT PULL] updates for tip


On Thu, 16 Apr 2009, Ingo Molnar wrote:

> 
> * Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > Ingo,
> > 
> > Please pull the latest tip/tracing/core tree, which can be found at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> > tip/tracing/core
> > 
> > 
> > Avadh Patel (1):
> >       tracing: add saved_cmdlines file to show cached task comms
> > 
> > Steven Rostedt (4):
> >       ftrace: use module notifier for function tracer
> >       tracing/events: add startup tests for events
> >       tracing/events: add rcu locking around trace event prints
> >       tracing/events/ring-buffer: expose format of ring buffer headers to users
> > 
> > ----
> >  include/linux/ftrace.h      |    7 --
> >  include/linux/module.h      |    4 +
> >  include/linux/ring_buffer.h |    5 +
> >  include/trace/ftrace.h      |    4 +
> >  kernel/module.c             |   19 ++---
> >  kernel/trace/ftrace.c       |   90 +++++++++++++-----
> >  kernel/trace/ring_buffer.c  |   44 +++++++++
> >  kernel/trace/trace.c        |   53 +++++++++++
> >  kernel/trace/trace_events.c |  214 +++++++++++++++++++++++++++++++++++++++++++
> >  9 files changed, 395 insertions(+), 45 deletions(-)
> 
> Pulled, thanks Steve!
> 
> I see one particular self-test failure - i've attached config and 
> dmesg snippet.
> 
> One thing becomes apparent from a quick glance at the dmesg: it's 
> not entirely obvious to see which event test failed. Here:
> 
>         sysname = kmalloc(4, GFP_KERNEL);
>         if (WARN_ON(!sysname)) {
>                 pr_warning("Can't allocate memory, giving up!\n");
>                 return 0;
>         }
>         memcpy(sysname, "*:*", 4);
>         ret = ftrace_set_clr_event(sysname, 1);
>         if (WARN_ON_ONCE(ret)) {
>                 kfree(sysname);
>                 pr_warning("error enabling all events\n");
>                 return 0;
>         }
> 
>         event_test_stuff();
> 
> we should probably print "sysname" in that failure path, right? 
> 
> This:
> 
> 	if (WARN_ONCE(KERN_CONT "%s: failed! ret: %d\n", sysname, ret)) {
> 		...
> 	}
> 
> would suffice, right?

The sysname is simply "*:*" to try to enable all calls. That was just me 
using the short cut to get it working, instead of enabling them all by 
hand.

I'm not sure showing "*:*" to the user would help in any way. There exists 
only one "all" case. We do print the system name for each system enable 
run 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/