linux-kernel - Re: [PATCH] tracing: Move tracepoint callbacks into DEFINE

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, 18 Aug 2009 15:11:04 -0700
From:	Josh Stone <jistone@...hat.com>
To:	Jason Baron <jbaron@...hat.com>
CC:	linux-kernel@...r.kernel.org, fweisbec@...il.com, mingo@...e.hu,
	laijs@...fujitsu.com, rostedt@...dmis.org, peterz@...radead.org,
	mathieu.desnoyers@...ymtl.ca, jiayingz@...gle.com,
	mbligh@...gle.com, lizf@...fujitsu.com
Subject: Re: [PATCH] tracing: Move tracepoint callbacks into DEFINE

On 08/18/2009 07:19 AM, Jason Baron wrote:
> this makes sense...Ingo also suggested having the two high level
> tracepoints be 'TRACE_EVENT' style. That is we should be able to
> register with the syscall entry and get the *all* the syscall numbers
> and arguments, and likewise on exit we should be able to get *all*
> syscall exit return values. see:
> 
> http://marc.info/?l=linux-kernel&m=125008740803571&w=2 
> 
> does this patch allow/do that?

It does allow this, and I am working on a patch to do it.  There are a
few naming conflicts between trace_syscalls.c and the stuff that ftrace
generates for "TRACE_EVENT(syscall_enter, ...)", but I will post soon
with a patch to resolve this.

Thanks,

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