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: <20110827102655.GJ2632@htj.dyndns.org>
Date:	Sat, 27 Aug 2011 12:26:55 +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, kay.sievers@...il.com
Subject: Re: [-v3 PATCH 0/3] Persistent device name using alias

(cc'ing Kay)
Hello,

On Sat, Aug 27, 2011 at 07:15:25PM +0900, Nao Nishijima wrote:
> Our concern is the failure analysis. For example, when the disk failure
> happened, we need to identify the disk from kernel log.
> 
> Kernel messages are output to serial console when kernel crashes.
> It's so hard to convert a device name to the alias. Thus the script
> can't always convert the name.

Hmm... I don't follow.  Why wouldn't it be able to?  All the
informations are in the log.  It is messy but it's there.  If you want
more structured information, u{dev|disks} already maintain device
libarary - what maps to what, connected how with what attributes and
so on.  Sending them off to the log machine as device hotplug events
occur and consulting it when post-processing log message would work
fine.  All you need is just some python scripting.  I don't really see
much point in messing with device names directly.  The only thing is
that the raw log would be prettier.  I don't think that is useful
enough to justify changing kernel device names.

Thanks.

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