Re: [PATCH v10 0/2] module: Extend module_blacklist parameter to built-in modules

On Fri, 4 Sep 2026 10:59:38 -0400 Aaron Tomlin [off-list ref] wrote:

On Thu, Sep 03, 2026 at 01:29:24PM -0700, Andrew Morton wrote:

quoted

On Thu,  3 Sep 2026 14:55:55 -0400 Aaron Tomlin [off-list ref] wrote:

quoted

Currently, the "module_blacklist=" command-line parameter only applies to
loadable modules. If a module is built-in, the parameter is silently
ignored. This patch series extends the blacklisting functionality to
built-in modules by intercepting their initialisation routines during early
boot.

Why?  What are the use-cases and what is the value of this change
to our users?

Important, so please don't skimp on the details.

Hi Andrew,

Thanks for asking.

Here is the rationale, concrete use cases, and the value this hopefully
brings to users and administrators.

...

In summary, this patch brings parity between modular and built-in drivers,
removes a pain point in boot-time disaster recovery, and provides users
with a predictable, consistent interface.

Really helpful, thanks.  Please add this to the [0/N] and maintain it.

I don't really know who are the potential audience for this change, nor
how to attract their attention.  Greg might have some insights but he
wasn't cc'ed.

Let's leave it a week to see if there's feedback then resend with these
adjustments?