linux-kernel - Re: [PATCH -tip v5 0/7] tracing: kprobe-based event tracer and x86 instruction decoder

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:	Mon, 11 May 2009 16:05:55 -0400
From:	Masami Hiramatsu <mhiramat@...hat.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	Ingo Molnar <mingo@...e.hu>, lkml <linux-kernel@...r.kernel.org>,
	Avi Kivity <avi@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>,
	Jim Keniston <jkenisto@...ibm.com>,
	"K.Prasad" <prasad@...ux.vnet.ibm.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	systemtap <systemtap@...rces.redhat.com>,
	kvm <kvm@...r.kernel.org>, Tom Zanussi <zanussi@...cast.net>
Subject: Re: [PATCH -tip v5 0/7] tracing: kprobe-based event tracer and x86
 instruction decoder

Steven Rostedt wrote:
> On Mon, 11 May 2009, Masami Hiramatsu wrote:
>>> Two high-level comments:
>>>
>>>  - There's no self-test - would it be possible to add one? See 
>>>    trace_selftest* in kernel/trace/
>> I'm not so sure. Currently, it seems that those self-tests are
>> only for tracers which define new event-entry on ring-buffer.
>> Since this tracer just use ftrace_bprintk, it might need
>> another kind of selftest. e.g. comparing outputs with
>> expected patterns.
>> In that case, would it be better to make a user-space self test
>> including filters and tracepoints?
> 
> Or have the workings in the selftest in kernel. As if a user started it. 
> It does not need to write to the ring buffer, that is just what I did. The 
> event selftests don't check if anything was written to the ring buffer, 
> they just make sure that the tests don't crash the system.

Would you mean that it is enough to enable some probes and just
see what happened at boot time?
That's so easy to add.

Thank you :-),

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division

e-mail: mhiramat@...hat.com

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