linux-kernel - Re: blktrace: event traces displayed wrong while ftrace blktrace is active

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: <20090414213207.GP955@mit.edu>
Date:	Tue, 14 Apr 2009 17:32:07 -0400
From:	Theodore Tso <tytso@....edu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Li Zefan <lizf@...fujitsu.com>, Jens Axboe <jens.axboe@...cle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: blktrace: event traces displayed wrong while ftrace blktrace
	is active

On Tue, Apr 14, 2009 at 11:25:33PM +0200, Frederic Weisbecker wrote:
> 
> Indeed. Note that you can overwrite this default by typing:
> 
> echo context-info > trace_option
> 
> after setting bkltrace as the current tracer.

The problem with doing that is that blktrace will then display this:

    fsync-tester-27934 [001]   208.031278:     fsync-tester-27934 [001]   208.031278: 254,4    Q  WS 268392 + 8 [fsync-tester]

I think the real problem is that blk trace is displaying the standard
context-info, so it's suppressing the normal context info.  So I have
the choice on having no context information on my event trace lines,
or two copies of the context information for the block trace lines.  

:-(

I'm guessing things were done this way in order to support the old
legancy blktrace format?

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