linux-kernel - Re: [PATCH] tracing/function-graph-tracer: make set_graph

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: <20090220144231.GB5732@nowhere>
Date:	Fri, 20 Feb 2009 15:42:32 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing/function-graph-tracer: make set_graph_function
	file support ftrace regex

On Fri, Feb 20, 2009 at 11:40:04AM +0100, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@...il.com> wrote:
> 
> > Impact: trace only functions matching a pattern
> > 
> > The set_graph_function file let one to trace only one or several
> > chosen functions and follow all their code flow.
> > 
> > Currently, only a constant function name is allowed so this patch
> > allows the ftrace_regex functions:
> > 
> > _ matches all functions that end with "name":
> >   echo *name > set_graph_function
> > 
> > _ matches all functions that begin with "name":
> >   echo name* > set_graph_function
> > 
> > _ matches all functions that contains "name":
> >   echo *name* > set_graph_function
> > 
> > Example:
> > 
> > echo mutex* > set_graph_function
> > 
> >  0)               |  mutex_lock_nested() {
> >  0)   0.563 us    |    __might_sleep();
> >  0)   2.072 us    |  }
> >  0)               |  mutex_unlock() {
> >  0)   1.036 us    |    __mutex_unlock_slowpath();
> >  0)   2.433 us    |  }
> >  0)               |  mutex_unlock() {
> >  0)   0.691 us    |    __mutex_unlock_slowpath();
> >  0)   1.787 us    |  }
> >  0)               |  mutex_lock_interruptible_nested() {
> >  0)   0.548 us    |    __might_sleep();
> >  0)   1.945 us    |  }
> > 
> > Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
> > ---
> >  kernel/trace/ftrace.c |   56 +++++++++++++++++++++++++++++++++---------------
> >  1 files changed, 38 insertions(+), 18 deletions(-)
> 
> Applied, thanks Frederic!
> 
> I'm wondering about the following: the whole set_graph_function 
> method is limited (to FTRACE_GRAPH_MAX_FUNCS, 32 entries), is 
> not scalable (we walk the array of functions at every function 
> trace point), has a separate API, etc.
> 
> Wouldnt we off better with a good, generic function attributes 
> hash, and an extension to the generic regexp parser to enable 
> the setting of those attributes? One such attribute could be the 
> 'expand child function'
> 
> 	Ingo

And well, you are answering this question I couldn't solve yesterday.
One of my goal was to be able to trace easily the syscalls:

echo sys_* > set_graph_function

But this array is static. And making it runtime resizable resulted in other problems:
locking? but doing that for each function is unacceptable. rcu was a good
candidate but I wonder that rcu would have been traced too, occuring tracing recursion.

Well, using such generic hashtable with such an attribute is really a good idea.

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