From: Greg KH <greg@kroah.com>
To: Nao Nishijima <nao.nishijima.xt@hitachi.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com, kay.sievers@vrfy.org,
jcm@redhat.com, coughlan@redhat.com, kzak@redhat.com,
dle-develop@lists.sourceforge.net,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
yrl.pp-manager.tt@hitachi.com, dgilbert@interlog.com,
stefanr@s5r6.in-berlin.de, hare@suse.de, joe@perches.com
Subject: Re: [PATCH v2 0/3] Persistent device name using alias name
Date: Fri, 22 Jul 2011 06:32:09 -0700 [thread overview]
Message-ID: <20110722133209.GA9522@kroah.com> (raw)
In-Reply-To: <20110722105925.7330.6609.stgit@ltc197.sdl.hitachi.co.jp>
On Fri, Jul 22, 2011 at 07:59:26PM +0900, Nao Nishijima wrote:
> Hi,
>
> This patch series provide an "alias name" of the disk into kernel messages.
> Users can assign a preferred name to an alias name of the device.
>
> 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 they 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 device name to alias name.
>
>
> Of course, I am going to modify the commands using device name so that users
> can use alias names.
Please do that first, and then you will not need any kernel changes in
the first place :)
Anyway, you all know my objections to this patch series, but again, as
I'm not the block subsystem maintainer, I really can't do anything.
greg k-h
next prev parent reply other threads:[~2011-07-22 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 10:59 [PATCH v2 0/3] Persistent device name using alias name Nao Nishijima
2011-07-22 10:59 ` [PATCH v2 1/3] sd: [BUGFIX] Use sd_printk instead of printk Nao Nishijima
2011-07-22 10:59 ` [PATCH v2 2/3] block: add a new attribute "alias name" in gendisk structure Nao Nishijima
2011-07-22 11:00 ` [PATCH v2 3/3] sd: modify printk for alias name Nao Nishijima
2011-07-22 13:32 ` Greg KH [this message]
2011-07-25 11:22 ` [PATCH v2 0/3] Persistent device name using " Karel Zak
2011-07-29 9:09 ` Nao Nishijima
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110722133209.GA9522@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=coughlan@redhat.com \
--cc=dgilbert@interlog.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=hare@suse.de \
--cc=jcm@redhat.com \
--cc=joe@perches.com \
--cc=kay.sievers@vrfy.org \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=nao.nishijima.xt@hitachi.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=yrl.pp-manager.tt@hitachi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox