From: Keerthy <a0393675@ti.com>
To: Eduardo Valentin <edubezval@gmail.com>, Rui Zhang <rui.zhang@intel.com>
Cc: Linux PM <linux-pm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/15] thermal: sysfs: add locking
Date: Wed, 1 Jun 2016 09:26:46 +0530 [thread overview]
Message-ID: <574E5CFE.6040708@ti.com> (raw)
In-Reply-To: <1464676296-5610-1-git-send-email-edubezval@gmail.com>
On Tuesday 31 May 2016 12:01 PM, Eduardo Valentin wrote:
> Hello,
>
> Several thermal sysfs entries are currently being called
> from userspace without locking. Data and calls to ops
> are accessed deliberated without any care for locking.
>
> This patch series attempts to fix this.
>
> Now that sysfs handlers are on the same place it is easier
> to visualize this issue and fix it. The strategy is essentially
> to lock any access. Also, functions in thermal core and thermal
> helpers are assumed to do the proper locking already.
>
> This patch series is based on the thermal core reorganization.
>
> There is no change in the ABI to userspace. The difference
> is that now serialization to data will be done.
>
> For your consideration, I am also adding this to this branch:
> git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal sysfs_locking
Tested and checked for reading temperatures from all the thermal zones
on DRA7/DRA72 and AM57XX-BEAGLE-X15 boards.
Also tested emulation using a rebased version of
https://lkml.org/lkml/2016/5/10/346
For DRA7/DRA72 and BEAGLE-X15:
Tested-by: Keerthy <j-keerthy@ti.com>
>
> Comments are welcome.
>
> BR,
>
> Eduardo Valentin (15):
> thermal: sysfs: lock tz in type_show
> thermal: sysfs: lock tz while on access to mode properties
> thermal: sysfs: lock tz while on trip_point_type properties
> thermal: sysfs: lock tz while on trip_point_temp properties
> thermal: sysfs: lock tz while on trip_point_hyst properties
> thermal: sysfs: lock tz while on passive properties
> thermal: sysfs: lock tz while on policy properties
> thermal: sysfs: improve locking of emul_temp_store()
> thermal: sysfs: lock tz when access sustainable power properties
> thermal: sysfs: lock tz when access tzp properties
> thermal: sysfs: lock cdev while accessing type
> thermal: sysfs: lock cdev while accessing max_state
> thermal: sysfs: lock cdev while accessing cur_state
> thermal: sysfs: serialize access to instances
> thermal: sysfs: add comments describing locking strategy
>
> drivers/thermal/thermal_sysfs.c | 133 ++++++++++++++++++++++++++++++++++------
> include/linux/thermal.h | 2 +-
> 2 files changed, 115 insertions(+), 20 deletions(-)
>
prev parent reply other threads:[~2016-06-01 3:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 6:31 [PATCH 00/15] thermal: sysfs: add locking Eduardo Valentin
2016-05-31 6:31 ` [PATCH 01/15] thermal: sysfs: lock tz in type_show Eduardo Valentin
2016-05-31 6:31 ` [PATCH 02/15] thermal: sysfs: lock tz while on access to mode properties Eduardo Valentin
2016-06-07 9:08 ` Keerthy
2016-06-07 9:22 ` Keerthy
2016-06-22 2:45 ` Zhang Rui
2016-06-22 5:06 ` [PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update Eduardo Valentin
2016-06-23 12:27 ` Rafael J. Wysocki
2016-06-23 12:37 ` Keerthy
2016-07-01 20:53 ` Eduardo Valentin
2016-06-22 5:15 ` [PATCHv2 " Eduardo Valentin
2016-06-22 9:33 ` Keerthy
2016-06-22 14:36 ` Eduardo Valentin
2016-06-22 15:05 ` Eduardo Valentin
2016-06-22 14:34 ` [PATCHv3 " Eduardo Valentin
2016-06-22 15:03 ` [PATCHv4 " Eduardo Valentin
2016-06-23 4:38 ` Keerthy
2016-06-23 4:51 ` Darren Hart
2016-06-29 6:23 ` Zhang Rui
2016-07-01 20:57 ` Eduardo Valentin
2016-07-03 9:03 ` Peter Feuerer
2016-07-02 2:49 ` [PATCHv2 1/1] thermal: sysfs: lock tz while on access to mode properties Eduardo Valentin
2016-05-31 6:31 ` [PATCH 03/15] thermal: sysfs: lock tz while on trip_point_type properties Eduardo Valentin
2016-05-31 6:31 ` [PATCH 04/15] thermal: sysfs: lock tz while on trip_point_temp properties Eduardo Valentin
2016-05-31 6:31 ` [PATCH 05/15] thermal: sysfs: lock tz while on trip_point_hyst properties Eduardo Valentin
2016-05-31 6:31 ` [PATCH 06/15] thermal: sysfs: lock tz while on passive properties Eduardo Valentin
2016-05-31 6:31 ` [PATCH 07/15] thermal: sysfs: lock tz while on policy properties Eduardo Valentin
2016-05-31 6:31 ` [PATCH 08/15] thermal: sysfs: improve locking of emul_temp_store() Eduardo Valentin
2016-05-31 6:31 ` [PATCH 09/15] thermal: sysfs: lock tz when access sustainable power properties Eduardo Valentin
2016-05-31 6:31 ` [PATCH 10/15] thermal: sysfs: lock tz when access tzp properties Eduardo Valentin
2016-05-31 6:31 ` [PATCH 11/15] thermal: sysfs: lock cdev while accessing type Eduardo Valentin
2016-05-31 6:31 ` [PATCH 12/15] thermal: sysfs: lock cdev while accessing max_state Eduardo Valentin
2016-05-31 6:31 ` [PATCH 13/15] thermal: sysfs: lock cdev while accessing cur_state Eduardo Valentin
2016-05-31 6:31 ` [PATCH 14/15] thermal: sysfs: serialize access to instances Eduardo Valentin
2016-05-31 6:31 ` [PATCH 15/15] thermal: sysfs: add comments describing locking strategy Eduardo Valentin
2016-06-01 3:56 ` Keerthy [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=574E5CFE.6040708@ti.com \
--to=a0393675@ti.com \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).