linux-kernel - Re: [PATCH 0/4] Various fixes and enhancements for tracing

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20081116065830.GF32215@elte.hu>
Date:	Sun, 16 Nov 2008 07:58:30 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] Various fixes and enhancements for tracing


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> This patchset applies on latest -tip (and normally against latest Steven's tracing tree).
> 
> _ tracing/ftrace: Fixes unexpected -EINVAL when longest tracer name is set
> _ tracing/ftrace: Change the type of the init() callback

applied to tip/tracing/ftrace,

> _ tracing/branch-tracer: Fix a trace recursion on branch tracer

applied to tip/tracing/branch-tracer,

> _ tracing/function-return-tracer: Support for dynamic ftrace on function return tracer

applied to tip/tracing/function-return-tracer.

thanks Frederic!

> The first and the third are bug fixes and the others are submitted 
> for purposes on improvement for tracing and the function return 
> tracer. Note that I kept the "return" name for the names used in the 
> last patch because we haven't yet decided what could be the better 
> name. But once we find it, I will change the name of data structures 
> and functions used by this tracer.

ok.

	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/