Re: [PATCH] init/main: Expose built-in initcalls and blacklist status via debugfs

On Sun, May 10, 2026 at 02:13:01AM -0400, Aaron Tomlin wrote:

At present, identifying the correct function name to supply to the
"initcall_blacklist=" kernel command-line parameter requires manual
inspection of the source code or kernel symbol tables. Furthermore,
administrators lack a reliable runtime mechanism to verify whether a
specified built-in module has been successfully blacklisted.

To resolve this, introduce a new debugfs interface at
/sys/kernel/debug/modules/builtin_initcalls. This file enumerates all
built-in modules alongside their corresponding initialisation callbacks
(e.g., those specified by module_init()) in a simple format:
"module_name init_callback". If a built-in module has been actively
blacklisted, the entry is explicitly appended with a " [blacklisted]"
suffix.

Dear maintainers,

I am writing to politely follow up on this patch, as it has been just over
a month since its initial submission.

To briefly reiterate, this patch introduces a reliable runtime mechanism to
identify built-in initcalls and verify their blacklisted status, thereby
significantly improving the usability of the "initcall_blacklist="
parameter.

I would be most grateful for any feedback, or to know whether any further
refinements are required for it to be considered for inclusion.

Kind regards,
-- 
Aaron Tomlin