On Feb 26, 2016 at 22:03 Al Viro wrote: And I'm not sure how
to deal with -o loop in a sane way, TBH - automagical losetup is bloody hard to get right.
See another reply in this thread for the idea: Fri, 26 Feb 2016 22:00:44 +0100
Keep in mind that loop-over-loop is also possible...
Indeed! Let's remember that mount(8) should never do it. # losetup /dev/loop0 /dev/sda2 # losetup /dev/loop1 /dev/loop0 # losetup -l NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE /dev/loop0 0 0 0 0 /dev/sda2 /dev/loop1 0 0 0 0 /dev/loop0 But it actually does, if the command line is "overlooped": oct:~ # mount -oloop /dev/loop1 /mnt as it does exactly that: oct:~ # losetup -l NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE /dev/loop0 0 0 0 0 /dev/sda2 /dev/loop1 0 0 0 0 /dev/loop0 /dev/loop2 0 0 1 0 /dev/loop1 It should definitely report error whenever trying -oloop on top of anything else than a file. Or at least a warning. Well, even losetup should report a warning. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxxx Lihovarská 1060/12 tel: +49 911 7405384547 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
