On Sat, Jul 11, 2026, at 01:13, Aaron Tomlin wrote:
> On Fri, Jul 10, 2026 at 05:59:59PM +0200, Arnd Bergmann wrote:
>> On Wed, Jul 8, 2026, at 04:00, Aaron Tomlin wrote:
>> > 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 extends the blacklisting functionality to built-in
>> > modules by intercepting their initialisation routines during early boot.
>>
>> Andrew already asked you to provide more background on what you need
>> this part for. Do you have a specific driver you need to disable?
>>
>> Can't you do the same thing using initcall_blacklist?
>
> The primary motivation for this patch is to provide consistent
> administrative control.
Ok, it sounds like you don't actually need it then.
> Regarding your suggestion to use initcall_blacklist=, while it is certainly
> a capable mechanism, it is fundamentally considered a debugging facility
> intended for developers.
I don't see much of a difference here, it's clearly still only a
debugging tool to me, not a general administrative interface: turning
off a random built-in driver likely causes undefined behavior later
if there are any other drivers (built-in or loaded) that depend on it.
Overall I don't think it's worth the added complexity.
Arnd
