[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-12-14 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.20.1-5.1ubuntu20.9 --- util-linux (2.20.1-5.1ubuntu20.9) trusty; urgency=medium * mount/lomount.c: Query /dev/loop-control for next free loopback device. (LP: #1640823) -- Thomas Voß Tue, 15 Nov

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-12-13 Thread Robie Basak
16:49 bdmurray: I hadn't looked at bug 1640823 again, no. Shall I review and release ifappropriate during my SRU day tomorrow? 16:50 rbasak: Since you had an opinion I think that's appropriate -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-11-28 Thread Martin Pitt
I successfully ran the test case against ubuntu20.9 in -proposed. I also verified that using losetup and mount on loop devices still works: $ sudo losetup -f --show debian-stretch-DI-alpha7-amd64-netinst.iso /dev/loop0 $ sudo mount /dev/loop0 /mnt mount: block device /dev/loop0 is

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-11-23 Thread Thomas Voß
Thanks for your detailed feedback, I revisited the patch (please see the diff here http://paste.ubuntu.com/23522718/). I think (1.) - (3.) are covered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-11-23 Thread Robie Basak
This felt unusually risk to me, so I took a look at the patch before releasing. I found a number of problems: 1. This patch leaks a file descriptor every time the new code path runs. loop_ctl_fd is opened but not closed. 2. "int devnr = -1" is defined but never used. 3. > ll->ncur =

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-11-15 Thread Martin Pitt
I successfully ran the test case with the packages from -proposed. The VM also still boots successfully and shows no other sign of trouble. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-11-15 Thread Martin Pitt
Hello Martin, or anyone else affected, Accepted util-linux into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util- linux/2.20.1-5.1ubuntu20.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-11-15 Thread Martin Pitt
** Description changed: trusty has a very old util-linux which does not yet know about /dev /loop-control to create arbitrarily many loop devices. This feature was introduced in Linux 3.1 already (i. e. before precise even). This is a showstopper for backporting snappy as that needs a lot

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-11-14 Thread Martin Pitt
For the record: Commit 0b14bf7a is not sufficient. That neither fixes "losetup" nor "mount -o loop", and systemd's .mount units also just get translated into a /bin/mount -o loop" call. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

2016-11-10 Thread Martin Pitt
** Description changed: trusty has a very old util-linux which does not yet know about /dev /loop-control to create arbitrarily many loop devices. This feature was introduced in Linux 3.1 already (i. e. before precise even). This is a showstopper for backporting snappy as that needs a lot