From: "Arnd Bergmann" <arnd@arndb.de>
To: "Aaron Tomlin" <atomlin@atomlin.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Petr Pavlu" <petr.pavlu@suse.com>,
da.gomez@kernel.org, "Sami Tolvanen" <samitolvanen@google.com>,
"Peter Zijlstra" <peterz@infradead.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
neelx@suse.com, da.anzani@gmail.com, sean@ashe.io,
chjohnst@mail.com, steve@abita.co, mproche@mail.com,
nick.lane@mail.com, Linux-Arch <linux-arch@vger.kernel.org>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] module: Extend module_blacklist parameter to built-in modules
Date: Fri, 10 Jul 2026 17:59:59 +0200 [thread overview]
Message-ID: <33171ccd-038b-4bb8-b796-f104a131c0ee@app.fastmail.com> (raw)
In-Reply-To: <20260708020007.55728-1-atomlin@atomlin.com>
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?
> To preserve the existing user-space ABI, "module_blacklist=" is kept
> as a legacy alias pointing to the same module_denylist variable.
It looks like the denylist is only introduced in the same patch?
That sounds more useful, but would better be done in a separate
change, and also needs a proper changelog text.
Arnd
prev parent reply other threads:[~2026-07-10 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 2:00 [PATCH v4] module: Extend module_blacklist parameter to built-in modules Aaron Tomlin
2026-07-10 15:42 ` Sami Tolvanen
2026-07-10 15:59 ` Arnd Bergmann [this message]
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=33171ccd-038b-4bb8-b796-f104a131c0ee@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=chjohnst@mail.com \
--cc=da.anzani@gmail.com \
--cc=da.gomez@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mproche@mail.com \
--cc=neelx@suse.com \
--cc=nick.lane@mail.com \
--cc=peterz@infradead.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=sean@ashe.io \
--cc=steve@abita.co \
/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