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

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

Date:	Fri, 15 Jul 2011 07:28:48 -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.
> 

OK I pulled in everything but patch 10, as that seemed to have an issue
with the message that David Ahern brought up. I left that one out as it
really wasn't necessary for the other patches. If you want to just
resend that one patch with an update, I can pull that one in too.

-- Steve

> 
> Thank you,
> 
> ---
> 
> Masami Hiramatsu (13):
>       perf probe: Support adding probes on offline kernel modules
>       perf probe: Add probed module in front of function
>       [RESEND]perf probe: Introduce debuginfo to encapsulate dwarf information
>       [RESEND]perf probe: Warn when more than two lines are given
>       [RESEND][CLEANUP]perf-probe: Move dwarf library routines to dwarf-aux.{c,h}
>       [RESEND][CLEANUP]perf probe: Remove redundant dwarf functions
>       [RESEND][CLEANUP]perf probe: Move strtailcmp to string.c
>       [RESEND][CLEANUP]perf probe: Rename DIE_FIND_CB_FOUND to DIE_FIND_CB_END
>       tracing/kprobe: Update symbol reference when loading module
>       tracing/kprobes: Support module init function probing
>       kprobes: Return -ENOENT if probe point doesn't exist
>       [CLEANUP]tracing/kprobes: merge trace probe enable/disable functions
>       [CLEANUP]tracing/kprobes: Rename probe_* to trace_probe_*
> 
> 
>  Documentation/trace/kprobetrace.txt     |    9 
>  kernel/kprobes.c                        |   33 +
>  kernel/trace/trace_kprobe.c             |  314 +++++++++----
>  tools/perf/Documentation/perf-probe.txt |    6 
>  tools/perf/Makefile                     |    2 
>  tools/perf/builtin-probe.c              |   14 -
>  tools/perf/util/dwarf-aux.c             |  663 +++++++++++++++++++++++++++
>  tools/perf/util/dwarf-aux.h             |  100 ++++
>  tools/perf/util/probe-event.c           |  165 +++++--
>  tools/perf/util/probe-event.h           |    1 
>  tools/perf/util/probe-finder.c          |  752 ++++---------------------------
>  tools/perf/util/probe-finder.h          |   43 +-
>  tools/perf/util/string.c                |   19 +
>  tools/perf/util/util.h                  |    1 
>  14 files changed, 1304 insertions(+), 818 deletions(-)
>  create mode 100644 tools/perf/util/dwarf-aux.c
>  create mode 100644 tools/perf/util/dwarf-aux.h
> 


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