losetup with mknod fails on jammy with kernel 5.15.0-69-generic

[Marcus Furlong]

[ Impact ]

 * Regression in the loop block driver in Jammy kernel
   between 5.15.0-67 to 5.15.0-68 (in v5.15.86 stable),
   due to a change in the default behavior (value) of
   kernel parameter `max_loop` (from 0 to 8) in commit:
   `loop: Fix the max_loop commandline argument treatment
   when it is set to 0` (comment #6).

 * Users of loop devices (major 7) with minor >= 8 now
   fail to `open()` a loop device created with `mknod()`.

 * This is a corner case, as most people use `losetup`
   with usual /dev/loopNUMBER (or `--find`) which are
   not affected as it uses a different code path.
   (`losetup` for `/dev/loopNOT-A-NUMBER` is affected.)

 * Workaround: kernel parameter `max_loop=0`.

[ Test Steps ]

 * Run the test cases (losetup and test-loop.c in comment #6):
   - max_loop not set (default)
   - max_loop=0
   - max_loop=8

 * Verify the default behavior (max_loop not set) is restored.

 * Verify the modified behavior (max_loop is set) is unchanged.

[ Regression Potential ]

 * Regressions would be limited to the loop block driver,
   more specifically its default behavior (but it's that now)
   or specific usage of max_loop parameter (tested; looks OK).

[ Other Info ]

 * Patch 1 [1] is not quite a fix, but adds CONFIG guards that
   Patch 2 [2] depends on. (Alternatively, a Patch 2 backport
   with that could be done, but Patch 1 seems trivial enough.)

 * The fix on Jammy is only Patch 2, with a trivial backport
   (that CONFIG option is not in Jammy/v5.15, only in v5.18).

 * The fix on Lunar is both patches; clean cherry-picks.

 * The fix on Mantic is both patches too,
   now in v6.5-rc3, which should be automatically incorporated
   as Mantic apparently will release with the 6.5 kernel [3]

   [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23881aec85f3219e8462e87c708815ee2cd82358
   [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb5faa99f0ce40756ab7bbbce4f16c01ca5ebd5a
   [3] https://discourse.ubuntu.com/t/introducing-kernel-6-5-for-the-23-10-mantic-minotaur-release

Original Description:
---

losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic

# fallocate -l 1G test
# mknod -m 660 /dev/loop8 b 7 8
# chown root:disk /dev/loop8
# losetup /dev/loop8 ./test
losetup: ./test: failed to set up loop device: Device or resource busy

Possibly as a result of this patch:
https://<email address hidden>/T/

which was introduced in 5.15.0-68:
http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz

On a machine prior to this change (no issue with losetup):
# cat /sys/module/loop/parameters/max_loop
0
# uname -r
5.15.0-58-generic

On a machine after the change (has losetup issue as described above):
# cat /sys/module/loop/parameters/max_loop
8
# uname -r
5.15.0-69-generic

So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel.

Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mauricio Faria de Oliveira (mfo)]

Possible workaround w/ losetup.

# uname -rv
5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023

# cat /sys/module/loop/parameters/max_loop
8

# losetup -nl | sort
/dev/loop0 0 0 1 1 /var/lib/snapd/snaps/lxd_24322.snap 0 512
/dev/loop1 0 0 1 1 /var/lib/snapd/snaps/snapd_18357.snap 0 512
/dev/loop2 0 0 1 1 /var/lib/snapd/snaps/core20_1822.snap 0 512

# ls -1 /dev/loop*
/dev/loop-control
/dev/loop0
/dev/loop1
/dev/loop2
/dev/loop3
/dev/loop4
/dev/loop5
/dev/loop6
/dev/loop7

# truncate -s 1g test1
# truncate -s 1g test2
# ls -lh test1 test2
-rw-r--r-- 1 root root 1.0G Apr 6 17:40 test1
-rw-r--r-- 1 root root 1.0G Apr 6 17:40 test2

# losetup /dev/loop7 test1
# losetup /dev/loop8 test2
losetup: /dev/loop8: failed to set up loop device: No such device or address

...

# losetup --show --find test1
/dev/loop3
# losetup --show --find test1
/dev/loop4
# losetup --show --find test1
/dev/loop5
# losetup --show --find test1
/dev/loop6
# losetup --show --find test1
/dev/loop8
# losetup --show --find test1
/dev/loop9
# losetup --show --find test1
/dev/loop10
# losetup --show --find test1
/dev/loop11
# losetup --show --find test1
/dev/loop12
# losetup --show --find test1
/dev/loop13
# strace -e ioctl losetup --show --find test1
ioctl(3, LOOP_CTL_GET_FREE) = 14
ioctl(4, LOOP_CONFIGURE, {fd=3, block_size=0, info={lo_offset=0, lo_number=0, lo_flags=0, lo_file_name="/root/test1", ...}}) = 0
/dev/loop14
+++ exited with 0 +++

# losetup -d /dev/loop3
# losetup -d /dev/loop4
# losetup -d /dev/loop5
# losetup -d /dev/loop6
# losetup -d /dev/loop8
# losetup -d /dev/loop9
# losetup -d /dev/loop10
# losetup -d /dev/loop11
# losetup -d /dev/loop12
# losetup -d /dev/loop13

# losetup /dev/loop8 test2
#

works now.

# cat /sys/module/loop/parameters/max_loop
8

[Mauricio Faria de Oliveira (mfo)]

Simpler workarounds:

For non-existing /dev/loopN devices, `losetup /dev/loopN image` should work (i.e., don't do `mknod /dev/loopN`).

For /dev/non-loopN devices, it doesn't (different code path), so the utility attached should help for now.

Details below.

...

# lsb_release -cs
jammy

# uname -rv
5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023

# cat /sys/module/loop/parameters/max_loop
8

# ls -1 /dev/loop*
/dev/loop-control
/dev/loop0
/dev/loop1
/dev/loop2
/dev/loop3
/dev/loop4
/dev/loop5
/dev/loop6
/dev/loop7

# grep loop /proc/devices
  7 loop

# truncate -s 1g test

Case 1) Existing /dev/loopN: LOOP_CTL_ADD is not called, open() fails (non-init mutex, apparently).

# mknod /dev/loop8 b 7 8
# strace -e openat,ioctl losetup /dev/loop8 test 2>&1 | grep -i loop
openat(AT_FDCWD, "/dev/loop8", O_RDWR|O_CLOEXEC) = -1 ENXIO (No such device or address)
openat(AT_FDCWD, "/dev/loop8", O_RDWR|O_CLOEXEC) = -1 ENXIO (No such device or address)
losetup: /dev/loop8: failed to set up loop device

Case 2) Non-existing /dev/loopN: LOOP_CTL_ADD is called, open() works.

# rm /dev/loop8

# strace -e openat,ioctl losetup /dev/loop8 test 2>&1 | grep -i loop
openat(AT_FDCWD, "/dev/loop-control", O_RDWR|O_CLOEXEC) = 3
ioctl(3, LOOP_CTL_ADD, 8) = 8
openat(AT_FDCWD, "/dev/loop8", O_RDWR|O_CLOEXEC) = 4
ioctl(4, LOOP_CONFIGURE, {fd=3, block_size=0, info={lo_offset=0, lo_number=0, lo_flags=0, lo_file_name="/root/test", ...}}) = 0

Case 3) Non-existing /dev/non-loopN: LOOP_CTL_ADD is not called, open() fails.

# strace -e openat,ioctl losetup /dev/mynameX test 2>&1 | grep -i loop
losetup: /dev/mynameX: failed to set up loop device

Case 4) Existing /dev/non-loopN with workaround tool (attached)

# gcc -o loop-ctl-add loop-ctl-add.c

# mknod /dev/mynameX b 7 42

# losetup /dev/mynameX test
losetup: /dev/mynameX: failed to set up loop device: No such device or address

# ./loop-ctl-add 42
Success on ioctl('/dev/loop-control', LOOP_CTL_ADD, 42)

# losetup /dev/mynameX test
#

works!

[Mauricio Faria de Oliveira (mfo)]

Marking linux-hwe-5.15 as Invalid as it follows linux 5.15
(will get the fix automatically from linux 5.15 from jammy).

[Mauricio Faria de Oliveira (mfo)]

Regression in Jammy
-------------------

Before:

$ uname -rv
5.15.0-67-generic #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023

$ truncate -s 1M disk.img
$ sudo mknod /dev/loopNaN b 7 8
$ sudo losetup /dev/loopNaN disk.img
$

$ sudo ./test-loop
$

...

After:

$ uname -rv
5.15.0-68-generic #75-Ubuntu SMP Fri Feb 24 13:01:57 UTC 2023

$ truncate -s 1M disk.img
$ sudo mknod /dev/loopNaN b 7 8
$ sudo losetup /dev/loopNaN disk.img
losetup: /dev/loopNaN: failed to set up loop device: No such device or address

$ sudo ./test-loop
open: /dev/loop8: No such device or address

...

Upstream stable release bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2005113

...

Test-case:

$ cat test-loop.c
#include <fcntl.h>
#include <stdio.h>
#include <linux/major.h>
#include <sys/stat.h>
#include <sys/sysmacros.h>

#define LOOP_MINOR 8

#define _DEV_LOOP(x) "/dev/loop" #x
#define DEV_LOOP(x) _DEV_LOOP(x)

int main() {
        int rc, fd;

        rc = mknodat(AT_FDCWD, DEV_LOOP(LOOP_MINOR), S_IFBLK | 0660,
                     makedev(LOOP_MAJOR, LOOP_MINOR));
        if (rc == -1) {
                perror("mknod: " DEV_LOOP(LOOP_MINOR));
                return 1;
        }

        fd = open(DEV_LOOP(LOOP_MINOR), O_RDWR, 0);
        if (fd == -1) {
                perror("open: " DEV_LOOP(LOOP_MINOR));
                return 1;
        }

        return 0;
}

$ gcc -o test-loop test-loop.c

[Mauricio Faria de Oliveira (mfo)]

Testing on Jammy:
---

The default behavior before the regression is restored/fixed.
The modified behaviors are unchanged.

$ lsb_release -cs
jammy

Original:

 $ uname -rv
 5.15.0-79-generic #86-Ubuntu SMP Mon Jul 10 16:07:21 UTC 2023

 $ cat /proc/cmdline
 ... root=... ro

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=0

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=8

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

Patched:
...

 $ uname -rv
 5.15.0-79-generic #86+lp2015400 SMP Mon Jul 24 21:46:01 UTC 2023

 $ cat /proc/cmdline
 ... root=... ro

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=0

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=8

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

[Mauricio Faria de Oliveira (mfo)]

Testing on Lunar:
---

The default behavior before the regression is restored/fixed.
The modified behaviors are unchanged.

$ lsb_release -cs
No LSB modules are available.
lunar

Original:

 $ uname -rv
 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023

 $ cat /proc/cmdline
 ... root=... ro

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=0

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=8

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

Patched:

 $ uname -rv
 6.2.0-27-generic #28+lp2015400 SMP PREEMPT_DYNAMIC Mon Jul 24 22:16:20 UTC 2023

 $ cat /proc/cmdline
 ... root=... ro

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=0

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=8

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

[Mauricio Faria de Oliveira (mfo)]

[J/L][PATCH 0/2] loop: fix regression from max_loop default value change
https://lists.ubuntu.com/archives/kernel-team/2023-July/141350.html

[Mauricio Faria de Oliveira (mfo)]

Testing on Jammy (PATCH v2):
---

The default behavior before the regression is restored/fixed.
The modified behaviors are unchanged.

$ lsb_release -cs
jammy

Original:

 $ uname -rv
 5.15.0-79-generic #86-Ubuntu SMP Mon Jul 10 16:07:21 UTC 2023

 $ cat /proc/cmdline
 ... root=... ro

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=0

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=8

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

Patched:
...

 $ uname -rv
 5.15.0-79-generic #86+lp2015400v2 SMP Tue Aug 1 22:15:34 UTC 2023

 $ cat /proc/cmdline
 ... root=... ro

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=0

 $ sudo ./test-loop
 $

...

 $ cat /proc/cmdline
 ... root=... ro max_loop=8

 $ sudo ./test-loop
 open: /dev/loop8: No such device or address

[Mauricio Faria de Oliveira (mfo)]

[J/L][PATCH v2 0/2] loop: fix regression from max_loop default value change
https://lists.ubuntu.com/archives/kernel-team/2023-August/141594.html

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/6.2.0-30.30 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar-linux' to 'verification-failed-lunar-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Mauricio Faria de Oliveira (mfo)]

Verification done on lunar-proposed.

$ lxc launch ubuntu:lunar lunar-loop --vm
$ lxc shell lunar-loop

# apt install -y gcc
# gcc -o test-loop test-loop.c

# add-apt-repository -y -p proposed
# apt-cache madison linux-image-6.2.0-30-generic
linux-image-6.2.0-30-generic | 6.2.0-30.30 | http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
linux-image-6.2.0-30-generic | 6.2.0-30.30 | http://security.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
# apt install -y linux-image-6.2.0-30-generic

# echo "GRUB_DEFAULT='Advanced options for Ubuntu>Ubuntu, with Linux 6.2.0-30-generic'" >/etc/default/grub.d/99-default.cfg
# update-grub
# reboot

# uname -rv
6.2.0-30-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 9 13:33:35 UTC 2023

...

default: works (fixed)

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.2.0-30-generic root=PARTUUID=a335a269-dd48-4d3a-907a-2d2a2c6d53d7 ro console=tty1 console=ttyS0 panic=-1

# ./test-loop
#

max_loop=0: works (expected)

# echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT max_loop=0"' >/etc/default/grub.d/99-maxloop.cfg
# update-grub && reboot

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.2.0-30-generic root=PARTUUID=a335a269-dd48-4d3a-907a-2d2a2c6d53d7 ro console=tty1 console=ttyS0 max_loop=0 panic=-1

# ./test-loop
#

max_loop=8: fails (expected)

# echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT max_loop=8"' >/etc/default/grub.d/99-maxloop.cfg
# update-grub && reboot

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.2.0-30-generic root=PARTUUID=a335a269-dd48-4d3a-907a-2d2a2c6d53d7 ro console=tty1 console=ttyS0 max_loop=8 panic=-1

# ./test-loop
open: /dev/loop8: No such device or address

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/5.15.0-83.92 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy-linux' to 'verification-failed-jammy-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Mauricio Faria de Oliveira (mfo)]

Verification done on jammy-proposed.

$ lxc launch ubuntu:jammy jammy-loop --vm
$ lxc shell jammy-loop

# apt update && apt install -y gcc
# gcc -o test-loop test-loop.c

# add-apt-repository -y -p proposed
# apt-cache madison linux-image-5.15.0-83-generic
linux-image-5.15.0-83-generic | 5.15.0-83.92 | http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
linux-image-5.15.0-83-generic | 5.15.0-83.92 | http://security.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages

# apt install -y linux-image-5.15.0-83-generic

# echo "GRUB_DEFAULT='Advanced options for Ubuntu>Ubuntu, with Linux 5.15.0-83-generic'" >/etc/default/grub.d/99-default.cfg
# echo "GRUB_FORCE_PARTUUID=" >>/etc/default/grub.d/99-default.cfg
# update-grub && reboot

# uname -rv
5.15.0-83-generic #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023

...

default: works (fixed)

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=16ad92d2-3cc7-4162-9ffe-b5c17b8acbe2 ro console=tty1 console=ttyS0

# ./test-loop
#

...

max_loop=0: works (expected)

# echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT max_loop=0"' >/etc/default/grub.d/99-maxloop.cfg
# update-grub && reboot

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=16ad92d2-3cc7-4162-9ffe-b5c17b8acbe2 ro console=tty1 console=ttyS0 max_loop=0

# ./test-loop
#

...

max_loop=8: fails (expected)

# echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT max_loop=8"' >/etc/default/grub.d/99-maxloop.cfg
# update-grub && reboot

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=16ad92d2-3cc7-4162-9ffe-b5c17b8acbe2 ro console=tty1 console=ttyS0 max_loop=8

# ./test-loop
open: /dev/loop8: No such device or address

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-nvidia-6.2/6.2.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-done-jammy-linux-nvidia-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-failed-jammy-linux-nvidia-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-nvidia-tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-done-lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed-lunar-linux-starfive'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-azure/5.15.0-1047.54 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-linux-azure'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-intel-iotg/5.15.0-1039.45 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to 'verification-done-jammy-linux-intel-iotg'. If the problem still exists, change the tag 'verification-needed-jammy-linux-intel-iotg' to 'verification-failed-jammy-linux-intel-iotg'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-riscv-5.15/5.15.0-1041.45~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-riscv-5.15' to 'verification-failed-focal-linux-riscv-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-linux-raspi'. If the problem still exists, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-azure/6.2.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar-linux-azure'. If the problem still exists, change the tag 'verification-needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Mauricio Faria de Oliveira (mfo)]

This bug has been fixed in Lunar and Jammy, but not yet marked Fix Released apparently due to an issue with the Launchpad bot (reported to the Launchpad team); leaving as Fix Committed so to trigger when the bot runs again for it.

linux (6.2.0-32.32) lunar; urgency=medium
...
  * losetup with mknod fails on jammy with kernel 5.15.0-69-generic
    (LP: #2015400)
    - loop: deprecate autoloading callback loop_probe()
    - loop: do not enforce max_loop hard limit by (new) default

@ https://launchpad.net/ubuntu/+source/linux/6.2.0-32.32

linux (5.15.0-83.92) jammy; urgency=medium
...
  * losetup with mknod fails on jammy with kernel 5.15.0-69-generic
    (LP: #2015400)
    - loop: do not enforce max_loop hard limit by (new) default

@ https://launchpad.net/ubuntu/+source/linux/5.15.0-83.92

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-nvidia-tegra-igx/5.15.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-nvidia-tegra-5.15/5.15.0-1017.17~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-tegra-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-xilinx-zynqmp/5.15.0-1024.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Brian Murray (brian-murray)]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-linux-mtk'. If the problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!