public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Sebastian Priebe <sebastian.priebe@konplan.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+
Date: Fri, 20 Jun 2025 17:41:45 +0200	[thread overview]
Message-ID: <2025062007-fall-brim-a7ba@gregkh> (raw)
In-Reply-To: <ZR0P278MB097497EF6CFD85E72819447E9F70A@ZR0P278MB0974.CHEP278.PROD.OUTLOOK.COM>

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

  parent reply	other threads:[~2025-06-20 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  7:28 BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+ Sebastian Priebe
2025-06-20  6:47 ` AW: " Sebastian Priebe
2025-06-20  6:53   ` gregkh
2025-06-20 15:41 ` gregkh [this message]
2025-06-23  6:49   ` Sebastian Priebe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025062007-fall-brim-a7ba@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=sebastian.priebe@konplan.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox