public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] Multi-threaded device probing
Date: Wed, 26 Jul 2006 10:42:36 -0600	[thread overview]
Message-ID: <20060726164235.GH22822@parisc-linux.org> (raw)
In-Reply-To: <20060726161647.GA9675@kroah.com>

On Wed, Jul 26, 2006 at 09:16:47AM -0700, Greg KH wrote:
> However, almost all distros now use persistant names for network devices
> due to the PCI Hotplug issue, so it isn't probably as bad as you might
> think.

Oh, for people using a distro, I'm sure it's no problem at all.  It's
the homebrew people I'm worried about ;-)

> > I still think we need a method of renaming block devices, but haven't
> > looked into it in enough detail yet.
> 
> That could get "interesting"...
> 
> But now that we all are using /dev/disk/ and it has persistant device
> names for block devices, I really don't think it's that big of a deal.

Actually, that's exactly why it's a big deal.  The kernel spits out
messages like:

                printk(KERN_DEBUG "%s: Mode Sense: %02x %02x %02x %02x\n",
                       diskname, buffer[0], buffer[1], buffer[2], buffer[3]);

where diskname is something like sda.  Now the user has to figure out
what sda means in terms of /dev/disk/ and in terms of scsi h:c:t:l and
in terms of which sticky label is on which drive.  If we let userspace
change the gendev's disk_name, that printk can be meaningful to the user
in at least one of those senses.


  reply	other threads:[~2006-07-26 16:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 20:30 [RFC PATCH] Multi-threaded device probing Greg KH
2006-07-25 21:09 ` Alexey Dobriyan
2006-07-25 21:27   ` Greg KH
2006-07-25 21:27 ` H. Peter Anvin
2006-07-25 22:00 ` Dmitry Torokhov
2006-07-26  7:28   ` Greg KH
2006-07-25 22:15 ` James Courtier-Dutton
2006-07-26  0:08   ` Stefan Richter
2006-07-26  7:27     ` Greg KH
2006-07-26  7:24   ` Greg KH
2006-07-25 22:57 ` Keshavamurthy Anil S
2006-07-26  7:22   ` Greg KH
2006-07-26  0:34 ` Stefan Richter
2006-07-26  7:31   ` Greg KH
2006-07-26 11:29     ` Matthew Wilcox
2006-07-26 16:16       ` Greg KH
2006-07-26 16:42         ` Matthew Wilcox [this message]
2006-07-26 16:46           ` Greg KH
2006-07-27  0:02 ` Arnd Bergmann
2006-07-27  0:20   ` Greg KH

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=20060726164235.GH22822@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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