linux-kernel - Re: [RFC] convert ftrace syscall tracer to TRACE

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: <20090509155742.GA6340@Krystal>
Date:	Sat, 9 May 2009 11:57:42 -0400
From:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To:	"Frank Ch. Eigler" <fche@...hat.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Jason Baron <jbaron@...hat.com>,
	Tom Zanussi <tzanussi@...il.com>, linux-kernel@...r.kernel.org,
	fweisbec@...il.com, laijs@...fujitsu.com, rostedt@...dmis.org,
	peterz@...radead.org, jiayingz@...gle.com, mbligh@...gle.com,
	roland@...hat.com
Subject: Re: [RFC] convert ftrace syscall tracer to TRACE_EVENT()

* Frank Ch. Eigler (fche@...hat.com) wrote:
> Hi -
> 
> On Sat, May 09, 2009 at 10:37:37AM +0200, Ingo Molnar wrote:
> > [...]
> > Firstly, it adds two new tracepoints to every system call. That is 
> > unnecessary - we already have the TIF flag based callbacks, and we 
> > can use the existing syscall attributes table to get to tracepoints 
> > - without slow down (or impacting) the fast path in any way.
> > [...]
> 
> However, as the TIF_SYSCALL_FTRACE and/or TIF_SYSCALL_TRACE flags are
> tied to a single consumer, it would limit the usefulness of the
> naturally multiple-client tracepoints, if they were made conditional
> on them.  Would you be interested in a proper reference-counting API?
> 

I've got this in my TIF_KERNEL_TRACE patchset. I think I should post it
as-is for RFC once more.

Mathieu

> - FChE

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
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/