linux-kernel - Re: disabling CONFIG_LED

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]

Date:   Wed, 14 Oct 2020 06:29:19 +0200
From:   Udo van den Heuvel <udovdh@...all.nl>
To:     Randy Dunlap <rdunlap@...radead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-leds@...r.kernel.org, Dan Murphy <dmurphy@...com>,
        Pavel Machek <pavel@....cz>
Subject: Re: disabling CONFIG_LED_CLASS



On 13-10-2020 18:03, Randy Dunlap wrote:
> On 10/13/20 8:53 AM, Randy Dunlap wrote:
>> [adding LED people + list]
>>
>> On 10/13/20 6:24 AM, Udo van den Heuvel wrote:
(...)
>>>> So how do I disable this stuff?
>>>>
> 
> I was able to disable LEDS_CLASS and NEW_LEDS after I disabled the following
> config symbols:
> 
> 
> --- xx64/config-def64	2020-10-13 08:53:56.050501724 -0700
> +++ xx64/.config	2020-10-13 08:58:12.439205389 -0700
> -CONFIG_MAC80211_LEDS=y
> -CONFIG_RFKILL_LEDS=y
> -# CONFIG_LED_TRIGGER_PHY is not set
> -CONFIG_INPUT_LEDS=y
> -# CONFIG_HID_LED is not set
> -# CONFIG_USB_LED_TRIG is not set
> -# CONFIG_USB_LEDS_TRIGGER_USBPORT is not set
> -CONFIG_LEDS_TRIGGERS=y
> -CONFIG_EEEPC_LAPTOP=y
> +# CONFIG_EEEPC_LAPTOP is not set
> 
> This last one was the biggest problem for me.
> I started with x86_64 defconfig.

# grep LED .config
# grep LEDS .config
# grep EEPC .config
# make oldconfig
(...)
*
* LED Support
*
LED Support (NEW_LEDS) [Y/?] (NEW) y
  LED Class Support (LEDS_CLASS) [M/y/?] (NEW) n

So we still are stuck.

Udo