Users of our software (singularity) were affected by this issue.
https://github.com/sylabs/singularity/issues/1499
For historic reasons (old kernels without /dev/loop-control), we have
been creating /dev/loopXX devices directly via mknod, if needed, before
using them.
After the backport of
** Description changed:
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-5.15 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
3 matches
Mail list logo
