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
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
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
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.
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 =
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.
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.
** 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
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.
** 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
10 matches
Mail list logo