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: <20090413233953.GA955@mit.edu>
Date:	Mon, 13 Apr 2009 19:39:53 -0400
From:	Theodore Tso <tytso@....edu>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
	Tom Zanussi <tzanussi@...il.com>,
	Li Zefan <lizf@...fujitsu.com>,
	Frédéric Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH, RFC 0/3] Improvements to the tracing documentation

On Tue, Apr 14, 2009 at 12:55:42AM +0200, Ingo Molnar wrote:
> 
> It could be worked around right now by converting it to an integer 
> but i think what we want is native support for kdev_t, together with 
> all the usual convenience forms of specifying it: sda1 should work 
> the same way as 8:1 or 0801. Even /dev/sda1 should be recognized in 
> a filter expression.

Yeah, I could just drop in the integer now, and and just have
TP_printk() display "(8, 2)" instead of "sda2".  It's really a
question of how far we want to take pretty-printing and parsing for
ftrace, I suppose.

But if we are going to have end-users use it, having real
pretty-printed names would be a good thing, IMHO.  Especially if
major/minor numbers start becoming completely random beasts, as some
have proposed.  (I think it's a terrible idea, but I'm clearly not
politically correct.  :-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ