All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Eduardo Valentin <eduardo.valentin@ti.com>, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/1] thermal: add a warning for temperature emulation feature
Date: Tue, 2 Apr 2013 12:05:43 -0400	[thread overview]
Message-ID: <515B01D7.30101@ti.com> (raw)
In-Reply-To: <1364909633.2190.42.camel@rzhang1-mobl4>

On 02-04-2013 09:33, Zhang Rui wrote:
> On Tue, 2013-03-26 at 17:38 -0400, Eduardo Valentin wrote:
>> Because this feature is for debuging purposes, it is highly
>> recommended to do not enable this on production systems.
>> This patch adds warnings for system integrators, so that
>> people are aware of this potential security issue.
>>
>> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
>> ---
>>   Documentation/thermal/sysfs-api.txt |    4 ++++
>>   drivers/thermal/Kconfig             |    5 +++++
>>   2 files changed, 9 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/thermal/sysfs-api.txt b/Documentation/thermal/sysfs-api.txt
>> index a9abb84..0a7d6df 100644
>> --- a/Documentation/thermal/sysfs-api.txt
>> +++ b/Documentation/thermal/sysfs-api.txt
>> @@ -265,6 +265,10 @@ emul_temp
>>   	Unit: millidegree Celsius
>>   	WO, Optional
>>
>> +	  WARNING: Be careful while enabling this option on production systems,
>> +	  because userland can easily disable the thermal policy by simply
>> +	  flooding this sysfs node with low temperature values.
>> +
>>   *****************************
>>   * Cooling device attributes *
>>   *****************************
>> diff --git a/drivers/thermal/Kconfig b/drivers/thermal/Kconfig
>> index a764f16..004e5f7 100644
>> --- a/drivers/thermal/Kconfig
>> +++ b/drivers/thermal/Kconfig
>> @@ -80,12 +80,17 @@ config CPU_THERMAL
>>
>>   config THERMAL_EMULATION
>>   	bool "Thermal emulation mode support"
>> +	default false
>
> we do not need this as any Kconfig option is set to 'n' by default.
>


Yeah, I know it is a NOP. But that was intentional, just make the warn 
shout aloud :-)

> Others seem okay to me and applied.

OK. Thanks.


>
> thanks,
> rui
>>   	help
>>   	  Enable this option to make a emul_temp sysfs node in thermal zone
>>   	  directory to support temperature emulation. With emulation sysfs node,
>>   	  user can manually input temperature and test the different trip
>>   	  threshold behaviour for simulation purpose.
>>
>> +	  WARNING: Be careful while enabling this option on production systems,
>> +	  because userland can easily disable the thermal policy by simply
>> +	  flooding this sysfs node with low temperature values.
>> +
>>   config SPEAR_THERMAL
>>   	bool "SPEAr thermal sensor driver"
>>   	depends on PLAT_SPEAR
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


      reply	other threads:[~2013-04-02 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 21:38 [PATCH 1/1] thermal: add a warning for temperature emulation feature Eduardo Valentin
2013-04-02 13:33 ` Zhang Rui
2013-04-02 16:05   ` Eduardo Valentin [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=515B01D7.30101@ti.com \
    --to=eduardo.valentin@ti.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.