(eoan-amd64)root@nosferatu:~# apt-get install klibc-utils=2.0.6-1ubuntu2 
(eoan-amd64)root@nosferatu:~# /sbin/losetup -vf
(eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf
Loop device is /dev/loop6
loop: can't get info on device /dev/loop6: No such device or address
(eoan-amd64)root@nosferatu:~# apt-get install klibc-utils=2.0.6-1ubuntu3 
(eoan-amd64)root@nosferatu:~# /sbin/losetup -vf
(eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf
Loop device is /dev/loop6

** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-done-eoan

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.

  losetup -f broken in 2.0.6-1ubuntu2

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Eoan:
  Fix Committed
Status in klibc source package in Focal:
  Fix Released

Bug description:

   * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt,
  as main(argc) is reset to zero, after ioctl() operations in a function
  call, quite unexpectadly.

  [Test Case]

   * $ sudo /usr/lib/klibc/bin/losetup -vf
  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-protection did not help.

   * 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



  [   11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 
  [   11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: 
  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) + 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]: @@@@@@@@@@@@@@@@@@@@ summary
  boot                 FAIL non-zero exit status 2

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to