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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 09 Nov 2009 16:34:07 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Thadeu Lima de Souza Cascardo <cascardo@...oscopio.com> CC: linux-kernel@...r.kernel.org, device@...ana.org, akpm@...ux-foundation.org, rubini@...dd.com, gregkh@...e.de Subject: Re: [PATCH 3/3] misc: use a proper range for minor number dynamic allocation On 11/09/2009 04:30 PM, Thadeu Lima de Souza Cascardo wrote: > The current dynamic allocation of minor number for misc devices has some > drawbacks. > > First of all, the range for dynamic numbers include some statically > allocated numbers. It goes from 63 to 0, and we have numbers in the > range from 1 to 15 already allocated. Although, it gives priority to the > higher and not allocated numbers, we may end up in a situation where we > must reject registering a driver which got a static number because a > driver got its number with dynamic allocation. Considering fs/dlm/user.c > allocates as many misc devices as lockspaces are created, and that we > have more than 50 users around, it's not unreasonable to reach that > situation. > > The proposed solution uses the not yet reserved range from 64 to 127. If > more devices are needed, we may push 64 to 16. > Again, why not push these up above 256? -hpa -- 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