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]

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

On Wed, Jul 26, 2006 at 12:31:32AM -0700, Greg KH wrote:
> I don't know enough about SCSI to say if this driver core patch will
> help them out or not.  At first glance it does, but the device order
> gets all messed up from what users are traditionally used to, so perhaps
> the scsi core will just have to stick with their own changes.

Right.  Networking is in the same boat ... unless they're using udev
or some other tool which renames network interfaces.  I'm not entirely
comfortable with the kernel forcing you to use some other tool in order
to maintain stable device names on a static setup.  Perhaps we need
either a CONFIG option or a boot option to decide whether to do parallel
pci probes.

I still think we need a method of renaming block devices, but haven't
looked into it in enough detail yet.
-
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/