BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+

BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+

[Sebastian Priebe]

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.

Thanks.
Sebastian

AW: BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+

[Sebastian Priebe]

Hello,

Could somebody please have a look to this request?
As I mentioned in my last mail the config option BLOCK_LEGACY_AUTOLOAD isn't default y in 5.15.179+.
This deviates from all other versions (6.1.y, 6.6.y, 6.12.y and mainline).

Please merge 451f0b6f4c44d7b649ae609157b114b71f6d7875 (block: default BLOCK_LEGACY_AUTOLOAD to y) to 5.15.y.

Best regards.
Sebastian

https://www.konplan.com
> -----Ursprüngliche Nachricht-----
> Von: Sebastian Priebe
> Gesendet: Montag, 16. Juni 2025 09:28
> An: stable@vger.kernel.org
> Cc: gregkh@linuxfoundation.org
> Betreff: BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+
> 
> 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.
> 
> Thanks.
> Sebastian

Re: AW: BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+

[gregkh]

On Fri, Jun 20, 2025 at 06:47:58AM +0000, Sebastian Priebe wrote:
> Hello,
> 
> Could somebody please have a look to this request?

It's only been 4 days, please give us a chance to catch up on things.
There hasn't even been a new 5.15.y release since you made this request.

Also, please do not top-post.

thanks,

greg k-h

Re: BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+

[gregkh]

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

AW: BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+

[Sebastian Priebe]

> -----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.