| 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
| ||
|
Date: Wed, 03 Sep 2008 18:45:40 +0200 From: Tejun Heo <tj@...nel.org> To: "H. Peter Anvin" <hpa@...or.com> CC: device@...ana.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Jens Axboe <jens.axboe@...cle.com> Subject: Re: regarding major number of block extended devt H. Peter Anvin wrote: > Tejun Heo wrote: >> To use ext devt, the system has to use udev for device numbers. As long >> as udev is used, the major number doesn't matter. > > I'm sorry, but that's simply false. There is a *lot* of code out there > that assumes you can determine what the device is by correlating the > major number with /proc/devices. Then, we're between the rock and hard place then as there also is a lot of code which assumes certain layout of sd or hd minor numbers. Keeping only the major numbers doesn't really resolve any problem. It may be able to mask a few but that can be more harmful than helpful. So, if a program expects certain major numbers, it won't be able to access the partitions which have overflowed to the extended area. If a program uses udev or sys hierarchy to walk through devices, it will be able to use them all. Isn't that much better than overflowing into the same major and hope that everything would work out okay? Thanks. -- tejun -- 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