linux-kernel - Re: [PATCH 2/4] zedtrace generic kernel filtering

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: <1235978989.7581.46.camel@charm-linux>
Date:	Mon, 02 Mar 2009 01:29:49 -0600
From:	Tom Zanussi <tzanussi@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/4] zedtrace generic kernel filtering


On Sat, 2009-02-28 at 10:26 +0100, Ingo Molnar wrote:
> * Tom Zanussi <tzanussi@...il.com> wrote:
> 
> > Add generic kernel filtering.
> > 
> > Signed-off-by: Tom Zanussi <tzanussi@...il.com>
> > 
> > ---
> >  kernel/trace/trace_binary/Makefile     |    2 +-
> >  kernel/trace/trace_binary/zed.c        |  103 +++++++++--
> >  kernel/trace/trace_binary/zed.h        |   15 ++
> >  kernel/trace/trace_binary/zed_filter.c |  301 ++++++++++++++++++++++++++++++++
> >  kernel/trace/trace_binary/zed_filter.h |   45 +++++
> >  kernel/trace/trace_binary/zed_sched.c  |    4 +
> >  6 files changed, 451 insertions(+), 19 deletions(-)
> >  create mode 100644 kernel/trace/trace_binary/zed_filter.c
> >  create mode 100644 kernel/trace/trace_binary/zed_filter.h
> 
> Nice!
> 

Thanks!

> This fits really nicely into the ftrace principles and i'd love 
> to see this feature merged into ftrace - would you be interested 
> in working on that? If so then you can find the latest tracing 

Sure, but I'm not too familiar with the ftrace code and wouldn't have
big blocks of time to devote to it, so if it's something that's needed
"right away", I'll probably have to defer to letting someone else adapt
the code if they wanted to.

> tree at:
> 
>     http://people.redhat.com/mingo/tip.git/README
> 
> Note that Steve added explicit field enumeration and 'raw' C 
> syntax tracepoints to the event tracer earlier today (partly 
> based on your ideas here), so that would be a good basis to 
> extend/enhance/fix, if you are interested.
> 

Yeah, I took a quick look and saw some nice improvements.  Anyway, the
filtering I did for this was basically a side-effect of the event
description stuff, which made the filtering relatively easy to do (and
the event description files give the user a way to list the available
fields).  What I'm wondering is if you're interested in the filtering
part alone or in the event description part as well, which I hadn't
thought of as separable (I guess I need to look at the current ftrace
code to see what's already there).

Thanks,

Tom

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