linux-kernel - Re: [-v3 PATCH 0/3] Persistent device name using alias

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: <20110825101602.GI3286@htj.dyndns.org>
Date:	Thu, 25 Aug 2011 12:16:02 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Nao Nishijima <nao.nishijima.xt@...achi.com>
Cc:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	Jens Axboe <axboe@...nel.dk>,
	James.Bottomley@...senPartnership.com,
	dle-develop@...ts.sourceforge.net,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	yrl.pp-manager.tt@...achi.com
Subject: Re: [-v3 PATCH 0/3] Persistent device name using alias

Hello,

On Thu, Aug 25, 2011 at 06:03:59PM +0900, Nao Nishijima wrote:
> This patch series provide an "alias" of the disk into kernel messages.
> 
> A raw device name of a disk does not always point a same disk at each boot-up
> time. Therefore, users have to use persistent device names, which udev creates
> to always access the same disk. However, kernel messages still display the raw
> device names.
> 
> My proposal is that users can use and see persistent device names which were
> assigned by themselves because users expect same name to point same disk
> anytime.
> 
> Why need to modify kernel messages?
> - We can see mapping of device names and persistent device names in udev log.
>   If those logs output to syslog, we can search persistent device name from
>   device name, but it can cause a large amount of syslog output.
> 
> - If we can use the persistent device names and can always see the same name on
>   the kernel log, we don't need to pay additional cost for searching and picking
>   a correct pair of device name and persistent device name from udev log.
> 
> - Kernel messages are output to serial console when kenel crashes, it's so hard
>   to convert a device name to the alias.

Just some general comments.  This may already be a horse which is
beaten to death but anyways...

I'm not really convinced this is something we need.  What we're
missing is structured error reporting which can be understood,
processed, presented and reacted by programs implementing system
management policies.  Such facility would be useful in general but for
block devices I think it's a must that we're sorely missing.

Free format kernel message is a very undiscoverable way of
communicating these information.  For developing and debugging, it's
fine.  It's easy, flexible and you don't really have to think too much
about what should be presented how.  For anything else, it's basically
horrible.

I don't really see what the point of this feature is.  For developing
and debugging, pretty names might be nice but almost completely
unnecessary.  For anything else, this falls way too short and can be
easily replaced by some smart scripting from userland.  After all,
matching different device names is the least of the worries when
trying to use kernel log for general management and post-processing w/
good amount of heuristics is necessary to be useful anyway.

So, FWIW, I object.

Thank you.

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