linux-kernel - Re: [PATCH 0/5] [GIP PULL] tracing/events/trace

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]

Message-ID: <20090605145219.GA14830@elte.hu>
Date:	Fri, 5 Jun 2009 16:52:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/5] [GIP PULL] tracing/events/trace_stack: various
	fixes


* Steven Rostedt <rostedt@...dmis.org> wrote:

> 
> Ingo,
> 
> Please pull the latest tip/tracing/ftrace-4 tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/ftrace-4
> 
> 
> Steven Rostedt (1):
>       tracing: add annotation to what type of stack trace is recorded
> 
> Steven Whitehouse (1):
>       tracing: fix multiple use of __print_flags and __print_symbolic
> 
> walimis (3):
>       tracing/trace_stack: fix the number of entries in the header
>       tracing/events: fix output format of kernel stack
>       tracing/events: fix output format of user stack
> 
> ----
>  include/trace/ftrace.h      |    2 ++
>  kernel/trace/trace_output.c |   35 ++++++++++++++++++-----------------
>  kernel/trace/trace_stack.c  |    2 +-
>  3 files changed, 21 insertions(+), 18 deletions(-)

Pulled, (including the previous branches), thanks a lot Steve!

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