losetup -f broken in 2.0.6-1ubuntu2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
klibc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* sudo /usr/lib/
[Test Case]
* $ sudo /usr/lib/
Loop device is /dev/loop20
loop: can't get info on device /dev/loop20: No such device or address
is bad.
Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug.
[Regression Potential]
* klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes.
* disabling cf-protection and stack-clash-
* building with gcc-8 does not exhibit the problem.
* the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code.
[Other Info]
* Original bug report
http://
...
[ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
[ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
loop: can't get info on device /dev/loop1: No such device or address
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) [6n+ mkdir result
+ set -x
+ read LINE
+ grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt
++ grep -q /rofs result/lsblk.txt
grep: result/lsblk.txt: No such file or directory
autopkgtest [21:45:45]: test boot: -------
autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - -
boot FAIL non-zero exit status 2
autopkgtest [21:45:45]: @@@@@@@
boot FAIL non-zero exit status 2
...
description: | updated |
description: | updated |
tags: | added: patch |
no longer affects: | gcc-9 (Ubuntu) |
no longer affects: | gcc-9 (Ubuntu Eoan) |
no longer affects: | gcc-9 (Ubuntu Focal) |
no longer affects: | linux (Ubuntu Focal) |
no longer affects: | linux (Ubuntu Eoan) |
no longer affects: | linux (Ubuntu) |
Changed in klibc (Ubuntu Focal): | |
status: | Fix Released → Confirmed |
Changed in klibc (Ubuntu Eoan): | |
status: | New → Confirmed |
This is a bit strange. FWIW, this test has never passed properly on focal, the test doesn't really test anything until the cloud images appear and they weren't there for the first couple of tests.