linux-kernel - Re: [PATCH 1/2] ftrace: Add separate handler for ftrace:function event

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:	Wed, 25 Nov 2015 11:19:56 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jiri Olsa <jolsa@...nel.org>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	David Ahern <dsahern@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...nel.org>
Subject: Re: [PATCH 1/2] ftrace: Add separate handler for ftrace:function
 event

On Wed, 25 Nov 2015 16:45:32 +0100
Jiri Olsa <jolsa@...nel.org> wrote:

> Having following commands running concurently:
> 
>   # perf record -e ftrace:function -a -o krava.data sleep 10
>   # perf record -e ftrace:function --filter 'ip == SyS_read' ls
> 
> will endup in the latter one failing on the filter
> rules and store all functions (in perf.data) as
> instructed by the first record instead of just
> SyS_read records.
> 
> The reason is that we don't check the ftrace_ops that
> triggered the event with event's ftrace_ops. Hence
> once running together the event from latter perf will
> get all the data of the event from the first one.
> 
> Fixing this by having separate handler for ftrace:function
> event that actualy checks ftrace_ops against event.

This seems redundant. I never understood the control_ops that perf uses
in the function tracing infrastructure. Why can't you just register the
event->ops and have that ops set the filtering? Then the ftrace
infrastructure will only call that event handler for the functions its
filtered on. Then you don't need to do it again. Right now ftrace
already does that with the generic "control_ops" that perf uses, but
now you are doing it again. Seems rather pointless.

I may need to spend some time looking at how perf uses the function
tracing, and perhaps we can remove a lot of this redundancy.

-- Steve

> 
> Signed-off-by: Jiri Olsa <jolsa@...nel.org>
> ---
--
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/