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:	Sun, 15 Mar 2009 05:44:05 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Jiaying Zhang <jiayingz@...gle.com>,
	Martin Bligh <mbligh@...gle.com>
Subject: Re: [RFC][PATCH 2/2] tracing/x86: basic implementation of syscall
	tracing for x86-64


* Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:

> * Ingo Molnar (mingo@...e.hu) wrote:
> > 
> > * Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
> > 
> > > * Frederic Weisbecker (fweisbec@...il.com) wrote:
> > >
> > > > Provide the ptrace hooks and arch specific syscall numbers 
> > > > to ftrace arch indepedant syscall numbers. For now it only 
> > > > supports 4 syscalls to provide an example.
> > > > 
> > > 
> > > Hi Frederic,
> > > 
> > > I already have the equivalent TIF_KERNEL_TRACE flag in my 
> > > LTTng tree added to every Linux architecture. You might want 
> > > to re-use this work rather than re-doing this. I don't mind 
> > > changing the flag name.
> > 
> > Yeah. Note that the TIF bits are just one part - there are other 
> > bits needed for HAVE_FTRACE_SYSCALLS arch support.
> > 
> > Also, i'd eventually expect the TIF bits to be converted to a 
> > tracehook callback, not spread it to other architectures.
> > 
> 
> The nice part about the TIF bit is that it permits adding this 
> syscall tracing feature without increasing the size of the 
> thread_info struct nor adding any extra tests in entry.S. Does 
> the tracehook callback have these features ?

yes. Tracehook just factors out common interfacing points - with 
one specific implementation for now: ptrace. For syscall tracing 
that means it wraps TIF_SYSCALL_TRACE in essence.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ