| 2016-11-10 14:56:52 |
Martin Pitt |
bug |
|
|
added bug |
| 2016-11-10 14:57:01 |
Martin Pitt |
nominated for series |
|
Ubuntu Trusty |
|
| 2016-11-10 14:57:01 |
Martin Pitt |
bug task added |
|
util-linux (Ubuntu Trusty) |
|
| 2016-11-10 14:57:09 |
Martin Pitt |
bug |
|
|
added subscriber Thomas Voß |
| 2016-11-10 14:57:13 |
Martin Pitt |
util-linux (Ubuntu): status |
New |
Fix Released |
|
| 2016-11-10 14:57:15 |
Martin Pitt |
util-linux (Ubuntu Trusty): status |
New |
Triaged |
|
| 2016-11-10 15:02:38 |
Martin Pitt |
description |
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 of loop mounts.
Support for loop-control got introduced in http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=0b14bf7a
SRU TEST CASE:
$ for i in `seq 20`; do echo $i; sudo losetup --find --show /etc/issue; done
With current trusty's util-linux this will only work for 8 loop devices and then start failing:
8
/dev/loop7
9
losetup: could not find any free loop device
[...]
With the proposed version, they should all work.
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. |
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 of loop mounts.
Support for loop-control got introduced in http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=0b14bf7a
SRU TEST CASE:
$ for i in `seq 20`; do echo $i; sudo losetup --find --show /etc/issue; done
With current trusty's util-linux this will only work for 8 loop devices and then start failing:
8
/dev/loop7
9
losetup: could not find any free loop device
[...]
With the proposed version, they should all work.
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
|
| 2016-11-10 15:14:08 |
Martin Pitt |
description |
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 of loop mounts.
Support for loop-control got introduced in http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=0b14bf7a
SRU TEST CASE:
$ for i in `seq 20`; do echo $i; sudo losetup --find --show /etc/issue; done
With current trusty's util-linux this will only work for 8 loop devices and then start failing:
8
/dev/loop7
9
losetup: could not find any free loop device
[...]
With the proposed version, they should all work.
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
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 of loop mounts.
Support for loop-control got introduced in http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=0b14bf7a
SRU TEST CASE:
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ sudo mount -o loop /etc/issue /mnt
With current trusty's util-linux this will fail with "could not find any free loop device". With the proposed version, this should "only" fail with "you must specify the filesystem type" (or try it on an actual file system image).
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
|
| 2016-11-10 15:14:15 |
Martin Pitt |
summary |
[trusty] limited to 8 loop devices |
[trusty] mount -o loop is limited to 8 loop devices |
|
| 2016-11-10 15:45:38 |
Martin Pitt |
description |
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 of loop mounts.
Support for loop-control got introduced in http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=0b14bf7a
SRU TEST CASE:
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ sudo mount -o loop /etc/issue /mnt
With current trusty's util-linux this will fail with "could not find any free loop device". With the proposed version, this should "only" fail with "you must specify the filesystem type" (or try it on an actual file system image).
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
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 of loop mounts.
Support for loop-control got introduced in http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=0b14bf7a
SRU TEST CASE: (FIXME: this does not actually get fixed with the above commit)
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ sudo mount -o loop /etc/issue /mnt
With current trusty's util-linux this will fail with "could not find any free loop device". With the proposed version, this should "only" fail with "you must specify the filesystem type" (or try it on an actual file system image).
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
|
| 2016-11-15 10:18:28 |
Martin Pitt |
description |
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 of loop mounts.
Support for loop-control got introduced in http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=0b14bf7a
SRU TEST CASE: (FIXME: this does not actually get fixed with the above commit)
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ sudo mount -o loop /etc/issue /mnt
With current trusty's util-linux this will fail with "could not find any free loop device". With the proposed version, this should "only" fail with "you must specify the filesystem type" (or try it on an actual file system image).
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
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 of loop mounts.
Support for loop-control got introduced later util-linux versions, but backporting full support for it (for losetup) is too intrusive. We only need a partial backport for "mount -o loop".
SRU TEST CASE:
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ dd if=/dev/zero of=/tmp/img bs=1M count=50
$ mkfs.ext2 -F /tmp/img
$ sudo mount -o loop /tmp/img /mnt
With current trusty's util-linux this will fail with "could not find any free loop device". With the proposed version, this should succeed, and "sudo losetup -a" should show "/dev/loop8: ... (/tmp/img)".
Now, reboot, disable loop-control with
sudo mv /dev/loop-control{,.disabled}
and run the test case again. Now "mount -o loop" should fail with "could not find any free loop device" (as before). Ensure that there are no hangs, infinite loops, etc.
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
|
| 2016-11-15 10:22:33 |
Martin Pitt |
description |
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 of loop mounts.
Support for loop-control got introduced later util-linux versions, but backporting full support for it (for losetup) is too intrusive. We only need a partial backport for "mount -o loop".
SRU TEST CASE:
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ dd if=/dev/zero of=/tmp/img bs=1M count=50
$ mkfs.ext2 -F /tmp/img
$ sudo mount -o loop /tmp/img /mnt
With current trusty's util-linux this will fail with "could not find any free loop device". With the proposed version, this should succeed, and "sudo losetup -a" should show "/dev/loop8: ... (/tmp/img)".
Now, reboot, disable loop-control with
sudo mv /dev/loop-control{,.disabled}
and run the test case again. Now "mount -o loop" should fail with "could not find any free loop device" (as before). Ensure that there are no hangs, infinite loops, etc.
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
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 of loop mounts.
Support for loop-control got introduced later util-linux versions, but backporting full support for it (for losetup) is too intrusive. We only need a partial backport for "mount -o loop".
SRU TEST CASE:
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ dd if=/dev/zero of=/tmp/img bs=1M count=50
$ mkfs.ext2 -F /tmp/img
$ sudo mount -o loop /tmp/img /mnt
With current trusty's "mount" package this will fail with "could not find any free loop device". With the proposed version, this should succeed, and "sudo losetup -a" should show "/dev/loop8: ... (/tmp/img)".
Now, reboot, disable loop-control with
sudo mv /dev/loop-control{,.disabled}
and run the test case again. Now "mount -o loop" should fail with "could not find any free loop device" (as before). Ensure that there are no hangs, infinite loops, etc.
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
|
| 2016-11-15 10:30:39 |
Martin Pitt |
util-linux (Ubuntu Trusty): status |
Triaged |
Fix Committed |
|
| 2016-11-15 10:30:41 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-11-15 10:30:44 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2016-11-15 20:42:24 |
Martin Pitt |
tags |
|
verification-done |
|
| 2016-11-23 09:39:56 |
Robie Basak |
tags |
verification-done |
verification-failed |
|
| 2016-11-23 09:42:33 |
Robie Basak |
description |
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 of loop mounts.
Support for loop-control got introduced later util-linux versions, but backporting full support for it (for losetup) is too intrusive. We only need a partial backport for "mount -o loop".
SRU TEST CASE:
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ dd if=/dev/zero of=/tmp/img bs=1M count=50
$ mkfs.ext2 -F /tmp/img
$ sudo mount -o loop /tmp/img /mnt
With current trusty's "mount" package this will fail with "could not find any free loop device". With the proposed version, this should succeed, and "sudo losetup -a" should show "/dev/loop8: ... (/tmp/img)".
Now, reboot, disable loop-control with
sudo mv /dev/loop-control{,.disabled}
and run the test case again. Now "mount -o loop" should fail with "could not find any free loop device" (as before). Ensure that there are no hangs, infinite loops, etc.
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
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 of loop mounts.
Support for loop-control got introduced later util-linux versions, but backporting full support for it (for losetup) is too intrusive. We only need a partial backport for "mount -o loop".
SRU TEST CASE:
First, use up all default 8 loop devices:
$ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done
Now try to use a 9th:
$ dd if=/dev/zero of=/tmp/img bs=1M count=50
$ mkfs.ext2 -F /tmp/img
$ sudo mount -o loop /tmp/img /mnt
With current trusty's "mount" package this will fail with "could not find any free loop device". With the proposed version, this should succeed, and "sudo losetup -a" should show "/dev/loop8: ... (/tmp/img)".
Now, reboot, disable loop-control with
sudo mv /dev/loop-control{,.disabled}
and run the test case again. Now "mount -o loop" should fail with "could not find any free loop device" (as before). Ensure that there are no hangs, infinite loops, etc.
ADDITIONAL REGRESSION CHECKING TEST CASES
1. Check that every type of losetup call documented in the losetup manpage still works correctly.
2. Check that mount and umount commands that use loop devices still work correctly.
REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. |
|
| 2016-11-23 09:45:01 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2016-11-28 09:39:19 |
Martin Pitt |
tags |
verification-failed |
verification-needed |
|
| 2016-11-28 09:43:50 |
Martin Pitt |
tags |
verification-needed |
verification-done |
|
| 2016-12-14 10:18:52 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-12-14 10:28:57 |
Launchpad Janitor |
util-linux (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
