linux-kernel - Re: [RFC PATCH] Multi-threaded device probing

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]

Date:	Wed, 26 Jul 2006 10:42:36 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Greg KH <greg@...ah.com>
Cc:	Greg KH <gregkh@...e.de>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] Multi-threaded device probing

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.

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