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
| ||
|
Message-ID: <47145B31.8080104@s5r6.in-berlin.de> Date: Tue, 16 Oct 2007 08:33:21 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Jeff Garzik <jeff@...zik.org> CC: Greg KH <greg@...ah.com>, Rob Landley <rob@...dley.net>, James Bottomley <James.Bottomley@...eleye.com>, Matthew Wilcox <matthew@....cx>, linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org, Jens Axboe <axboe@...e.de>, Suparna Bhattacharya <suparna@...ibm.com>, Nick Piggin <piggin@...erone.com.au> Subject: Re: What still uses the block layer? Jeff Garzik wrote: > Greg KH wrote: >> On Mon, Oct 15, 2007 at 03:36:15AM -0500, Rob Landley wrote: >>> The point I was trying to make is that it seems to me like it would >>> be possible to keep the namespace separate here, and thus reduce the >>> enumeration problems to the point where common cases (like my laptop) >>> aren't impacted by them during early boot. >> >> Proposals on how to do this would be gladly reviewed. > > Agreed. - move the networking core's facilities to build the default name of an interface into lib/ - expand it to optionally use base-26 numbering (a...nn...zzz) as alternative to decimal numbering - let SCSI low-level drivers optionally provide a short constant string, resembling its transport name, in the host template or transport template - let SCSI high-level driver make use of the new naming functions in lib/, providing either just "sd", "sr" etc. or "sd-$transport-" as name prefix No patch yet, and alas I'm currently short of spare time. -- Stefan Richter -=====-=-=== =-=- =---- http://arcgraph.de/sr/ - 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/
Powered by blists - more mailing lists