linux-kernel - Re: how to disable the button kernel module?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0780918b-184e-55a6-a439-06403d3777ff@infradead.org>
Date:   Thu, 14 Nov 2019 21:33:10 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bruno GNUser <kernel@...tas.airpost.net>,
        linux-kernel@...r.kernel.org,
        ACPI Devel Mailing List <linux-acpi@...r.kernel.org>
Subject: Re: how to disable the button kernel module?

On 11/14/19 4:00 AM, Bruno GNUser wrote:
> I realize that /button/ is a kernel built-in and therefore cannot be disabled
> via the /blacklist=<module_name>/ boot parameter. So I thought I'd try
> /initcall_blacklist=<function>/ but I cannot find an obvious module
> initialization function in button.c

In what kernel version if the button driver built-in?
It currently can be built as a loadable module.

The lines
module_driver(acpi_button_driver, acpi_button_register_driver,
	       acpi_button_unregister_driver);
at the end of the source file create an init function named
acpi_button_driver_init.  You could try:
  initcall_blacklist=acpi_button_driver_init


> Please, how would one disable the /button/ module? Either using the
> /initcall_blacklist=foo/ or some other method is fine, as long as it does
> not involve recompiling the kernel. 

Any help from ACPI people?


> Thanks,
> Bruno GNUser
> 
> 
> --
> Sent from: http://linux-kernel.2935.n7.nabble.com/


-- 
~Randy