linux-kernel - Re: [PATCH] Modify loop device to be able to manage partitions of the disk image

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: <47CFE1B9.1080405@draigBrady.com>
Date:	Thu, 6 Mar 2008 12:21:13 +0000
From:	Pádraig Brady <P@...igBrady.com>
To:	Laurent Vivier <Laurent.Vivier@...l.net>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Modify loop device to be able to manage partitions of
 the disk image

Laurent Vivier wrote:
> Le jeudi 06 mars 2008 à 11:34 +0000, Pádraig Brady a écrit :
>> Laurent Vivier wrote:
>>> This patch allows to use loop device with partitionned disk image.
>>>
>>> Original behavior of loop is not modified.
>>>
>>> A new parameter is introduced to define how many partition we want to be
>>> able to manage per loop device. This parameter is "max_part".
>> I like it!
> 
> Thanks,
> 
>> Shouldn't we set max_part to non zero by default though?
> 
> Well, the problem is that you modify the default minor number of loop
> device if max_part != 0, so I'm afraid of compatibility problems:

I understand that. But who would care about specific minor numbers?
Hmm how does your patch relate to this: http://lwn.net/Articles/110426/

As an aside, I also notice on my system from the following output that
the limit of the number of partitions for a sata/scsi disk seems to be 15:

$ ls -la /dev/sd[ab]
brw-rw---- 1 root disk    8,  0 2007-11-13 10:35 /dev/sda
brw-rw---- 1 root plugdev 8, 16 2008-03-06 12:11 /dev/sdb

Pádraig.
--
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/