linux-kernel - Re: regarding major number of block extended devt

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: <48BE0EDB.20107@kernel.org>
Date:	Wed, 03 Sep 2008 06:13:15 +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:
>>  259 block    Block extended device numbers
>>
>>         This is pool of dynamically allocated block device
>>         numbers.  Currently, ide and sd overflows into this
>>         region if there are more partitions than the existing
>>         device number scheme can accomodate, but any block
>>         device can use it and it's not restricted to
>>         overflows.
>>
> 
> It would seem better to simply use the high minors on the
> already-existing ide and scsi majors?

I thought it would be better to break from those majors to make it clear
that the traditional minor allocation scheme isn't followed anymore.
Programs which expect certain majors are likely to need update for how
it deals with minors, so....

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/