linux-kernel - Re: [PATCH] blktrace: move trace/ dir to /sys/block/sda/

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: <20090413201155.GA17450@elte.hu>
Date:	Mon, 13 Apr 2009 22:11:55 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Tom Zanussi <tzanussi@...il.com>
Cc:	Li Zefan <lizf@...fujitsu.com>, Theodore Ts'o <tytso@....edu>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] blktrace: move trace/ dir to /sys/block/sda/


* Jens Axboe <jens.axboe@...cle.com> wrote:

> On Mon, Apr 13 2009, Li Zefan wrote:
> > Impact: allow ftrace-plugin blktrace to trace device-mapper devices
> > 
> > blktrace can't trace a single partition, so it makes no sense to
> > have one trace/ dir in each /sys/block/sda/sdaX. Move it to
> > /sys/block/sda/.
> > 
> > Thus we fix an issue reported by Ted, that ftrace-plugin 
> > blktrace can't be used to trace device-mapper devices.
> 
> Perhaps I never committed that patch, but it would be trivial to 
> do partition based blktrace tracing. It's also quite useful. So 
> please don't go changing things to make that harder to support, it 
> would be nicer to just add the (small) bits to support 
> per-partition tracing. It's basically just a start/stop sector 
> range, while some events are per-device and should just be 
> included always.

btw., per tracepoint filters could be used for that. That would 
allow multiple partitions to be traced at once.

blktrace user-space could make use of sector range filters straight 
away [ hm, Tom - do we have the <= comparison operator already, or 
is that still WIP? ] - but i think it's better to do this in a more 
integrated way: via the sysfs API, via /sys/block/sda/sda2/trace/.

So when a partition's trace entry is activated, it would 
auto-install a specific filter expression for sda, with the sector 
range of that partition. Or something like that. How does this 
sound?

	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/