linux-ext4 - Re: [ltt-dev] Fw: [PATCH] ext4: Add markers for better debuggability

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 9 Jan 2009 13:58:40 -0500
From:	Theodore Tso <tytso@....edu>
To:	Mathieu Desnoyers <compudj@...stal.dyndns.org>
Cc:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	ltt-dev@...ts.casi.polymtl.ca,
	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [ltt-dev] Fw: [PATCH] ext4: Add markers for better
	debuggability

On Fri, Jan 09, 2009 at 09:49:01AM -0500, Mathieu Desnoyers wrote:
> 
> Given this is meant to be in the mainline kernel, using tracepoints
> rather than markers would be more appropriate. Please see
> Documentation/tracepoints.txt and samples/tracepoints/ for details.

I saw that, but I'm still not sure how I would actually *use*
tracepoints.  I can use markers today with Systemtap, and I need an
easy way to be able to selectively do things like "trap and print all
of the logged data when the ext4_request_inode tracepoint/marker is
tripped where dev=='dm-8'".

Unfortunately, Systemtap seems doomed given its current course and
direction, so I'm not opposed to moving to another solution --- I just
need a HOWTO that demonstrates how I can do this painlessly and
easily; preferably without having me have to manually hack up a kernel
module each time I want to implement the tracing

Is there an easy way to do that using ltt today?  Can you point me at
a sample of how this could be done?

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html