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  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:   Fri, 7 Aug 2020 11:40:02 +0200
From:   Daniel Lezcano <>
To:     Linus Torvalds <>
Cc:     Zhang Rui <>,
        Amit Kucheria <>,
        Andrzej Pietrasiewicz <>,
        Colin King <>,
        Shawn Guo <>,
        Lukasz Luba <>,
        Sumeet Pawnikar <>,
        Henry Yen <>,
        Thierry Reding <>,
        Linux Kernel Mailing List <>,
        Linux PM mailing list <>,
        Marian-Cristian Rotariu 
Subject: Re: [GIT PULL] RESEND: thermal for v5.9-rc1

Hi Linus,

On 07/08/2020 04:43, Linus Torvalds wrote:
> On Thu, Aug 6, 2020 at 1:19 PM Daniel Lezcano <> wrote:
>> - Add generic netlink support for userspace notifications: events,
>> temperature
>>   and discovery commands (Daniel Lezcano)
> This is "default y".
> Why?
> The help text doesn't explain either.
> Please explain, or remove the default y. We don't add new features and
> then try to force people to use them by enabling them by default.
> "default y" is mainly for when something unconditional gets split up
> and becomes conditional (so now "default y" means that you don't break
> peoples setups when they don't even know what it is).
> Alternatively, "default y" is for things that are make peoples lives
> immeasurably better somehow, and it would be a crime to not enable it
> because it's _so_ wonderful.

Well, I won't argue the netlink notification is so that fantastic but it
is a feature that was needed since a long time. A previous partial
implementation was directly compiled-in and then removed [1] because
there were no user as it is and we wanted to introduce a clean new
notification framework based in our previous discussion at Linux
Plumbers Conference [2] but that needed some cleanups of the thermal
core code before.

This netlink framework fulfills the needs of the thermal daemons for
Intel, Android HAL and SoC vendors which are hacking the thermal
framework or constantly polling the temperature.

Because the compilation failed if CONFIG_NET=n, the Kconfig option was
introduced afterwards [3]. It could have been directly handled in the
code with a 'ifdef' directive without option but it sounded more
convenient to at least give the opportunity to opt-out the notification.

It defaults to 'y' because the previous (but unused) implementation was
unconditionally compiled-in and because of the thermal users needs.

Is default=y wrong given this history?

 -- Daniel


> So far, I'm not convinced we've ever hit that second case.
> Convince me that the thermal layer is so magical that it really
> warrants it. Tell me why and how my life is improved by enabling it.
>              Linus

<> │ Open source software for ARM SoCs

Follow Linaro:  <> Facebook |
<!/linaroorg> Twitter |
<> Blog

Powered by blists - more mailing lists