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]

Date:	Thu, 6 Mar 2008 07:35:51 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Laurent Vivier <Laurent.Vivier@...l.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Modify loop device to be able to manage partitions of
	the disk image

On Thu, Mar 06, 2008 at 10:43:32AM +0100, 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've done something else before as have done others, but at that time
we didn't want it in because it breaks the device number encoding.

Nowdays where a lot of systems use udev it probably makes sense to put
it in.  The default is to not show any partitions which is safe.  Did
you test if udev is smart enough to find out loop has partitions when
loaded with the paramater?  If yes this can go in with a little
documentation added, if not please also work with the udev folks to
find a way to automatically detect that loop can sometimes support
partitions.
--
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/