linux-kernel - Re: [PATCH][v2] Modify loop device to be able to manage partitions

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 07 Mar 2008 21:34:51 +0100
From:	devzero@....de
To:	Laurent.Vivier@...l.net
Cc:	breeves@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][v2] Modify loop device to be able to manage partitions

>Of course, the same behavior can be done using kpartx on a loop device,
>but modifying loop avoids to stack several layers of block device (loop +
>device mapper), this is a very light modification (40% of modifications
>are to manage the new parameter).

iirc, patches like this have been submitted more than once.
i remember i have seen one floating around years ago.

aside from the fact that using partitions on loop devices is useful - if 
we had dm-loop (http://sources.redhat.com/lvm2/wiki/DMLoop) in mainline - 
would using kpartx with that also mean stacking 2 layers of block device ?

personally, i like the kpartx approach. afaik, it`s working good.

i also like dm-loop, because i think that mapping of files to blockdevices 
belongs into an appropriate subsystem like device-mapper.

maybe some of the dm folks know better or have some real arguments - so i`m 
adding bryn reeves here. (just noticed that dm-loop disappeared from -mm due 
to removal of some api change - so it`s a good chance to bring it back into 
discussion) ;)

regards
roland

_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220

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