-----Ursprüngliche Nachricht----- Von: gregkh@linuxfoundation.org gregkh@linuxfoundation.org Gesendet: Freitag, 20. Juni 2025 17:42 An: Sebastian Priebe sebastian.priebe@konplan.com Cc: stable@vger.kernel.org Betreff: Re: BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+
On Mon, Jun 16, 2025 at 07:28:25AM +0000, Sebastian Priebe wrote:
Hello,
we're facing a regression after updating to 5.15.179+. I've found that fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296 (block: deprecate
autoloading based on dev_t) was merged that disabled autoloading of modules.
This broke mounting loopback devices on our side.
Why wasn't 451f0b6f4c44d7b649ae609157b114b71f6d7875 (block: default
BLOCK_LEGACY_AUTOLOAD to y) merged, too?
This commit was merged for 6.1.y, 6.6.y and 6.12y, but not for 5.15.y.
Please consider merging this for 5.15.y soon.
I'll queue this up now, but note, unless you are starting with a new fresh .config file, the default value change will probably not be noticed by 'make oldconfig' so you would probably have still hit this issue.
thanks,
greg k-h
Hello, thanks a lot. We're using a custom defconfig in our build environment so this should work. But I will have an eye on it.