| 2023-03-28 14:08:41 |
Jasper Spaans |
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 |
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://github.com/archlinux/svntogit-packages/blob/62b8243b1d485493d3e8b10b05281efa20fe7918/trunk/config#L2517 |
|
