Public bug reported: Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter.
In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means no more than 8 loop devices are supported. This is a regression. At least one other distro solves this by compiling with CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 [1]; maybe Ubuntu could start doing that as well. We currently workaround this by setting max_loop=0 on the kernel cmdline but would rather not have to. [1] https://aur.archlinux.org/cgit/aur.git/tree/config?h=linux-lts515#n2492 ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013086 Title: regression: max number of loop devices Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter. In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means no more than 8 loop devices are supported. This is a regression. At least one other distro solves this by compiling with CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 [1]; maybe Ubuntu could start doing that as well. We currently workaround this by setting max_loop=0 on the kernel cmdline but would rather not have to. [1] https://aur.archlinux.org/cgit/aur.git/tree/config?h=linux-lts515#n2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2013086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
