linux-kernel - Re: [PATCH -tip 00/13]tracing/kprobes: Dynamic events on module support

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, 28 Jun 2011 09:18:25 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, yrl.pp-manager.tt@...achi.com
Subject: Re: [PATCH -tip  00/13]tracing/kprobes: Dynamic events on module
 support

On Mon, 2011-06-27 at 16:26 +0900, Masami Hiramatsu wrote:
> Hi Steven,
> 
> Here, I'd like to push updates of dynamic events and perf-probe
> for supporting dynamic events on module.
> 
> The main part of this series is 1-5th patches for kprobes and
> dynamic event tracer, which allows us to add events on offline
> kernel module. This means we can put events even on the init
> functions of the drivers before loading. The requirement of
> this feature comes from my recent experience of a driver
> debugging. It had a timing bug in the initialization routine,
> and it was hard to catch them without tracing the behavior.
> 
> I added some perf-probe updates (which including some resent
> patches), And it's OK to pull only the main part (kprobes and
> ftrace patches) without perf updates.
> 

Thanks Masami,

I'll try to get to this this week. I've just been doing my main job at
the moment ;) Which surprisingly, has nothing to do with ftrace.

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