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] [day] [month] [year] [list]

Date:	Fri, 07 Mar 2008 13:13:56 +0100
From:	Laurent Vivier <Laurent.Vivier@...l.net>
To:	7eggert@....de
Cc:	Nick Piggin <nickpiggin@...oo.com.au>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Modify loop device to be able to manage partitions of
	the disk image


Le vendredi 07 mars 2008 à 12:56 +0100, Bodo Eggert a écrit :
> Nick Piggin <nickpiggin@...oo.com.au> wrote:
> > On Thursday 06 March 2008 21:16, Laurent Vivier wrote:
> >> Le jeudi 06 mars 2008 à 20:57 +1100, Nick Piggin a écrit :
> 
> >> > Do you think we do something similar for drivers/block/brd.c too? I'd
> >> > like to try to maintain parity between them where possible...
> >>
> >> I think it is possible  (I've the same patch for NBD too), but I think
> >> it is completely useless.
> > 
> > It's useful for testing, and for minimising the divergence in the
> > code.
> 
> Maybe there should be a common mechanism to use partitions on any block
> device. Maybe there is - I have dark memories about the device mapper

The mechanism exists: the driver must call alloc_disk() with a value !=
1. This is what is modifying this patch.

> being able to parse partition tables, and plans on moving partition
> support to userspace.

This is kpartx.

Laurent
-- 
----------------- Laurent.Vivier@...l.net  ------------------
"Programmers who subconsciously view themselves as artists
 will enjoy what they do and will do it better." D. Knuth

--
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/