All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Thara Gopinath <thara.gopinath@linaro.org>,
	edubezval@gmail.com, daniel.lezcano@linaro.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] thermal: Fix locking in cooling device sysfs update cur_state
Date: Thu, 03 Jan 2019 10:51:22 +0800	[thread overview]
Message-ID: <1546483882.2077.10.camel@intel.com> (raw)
In-Reply-To: <5C2D7376.3010408@linaro.org>

On 三, 2019-01-02 at 21:29 -0500, Thara Gopinath wrote:
> On 11/27/2018 05:43 PM, Thara Gopinath wrote:
> > 
> > Sysfs interface to update cooling device cur_state does not
> > currently holding cooling device lock sometimes leading to
> > stale values in cur_state if getting updated simultanelously
> > from user space and thermal framework. Adding the proper locking
> > code fixes this issue.
> > 
> > Signed-off-by: Thara Gopinath <thara.gopinath@linaro.org>
> > ---
> > 
> > V1->V2: Rearranged the code as per Daniel's  review comment 
> Hi Eduardo, Daniel
> 
> Any comments on this ?
> 
it's already in my tree, and will be included in my pull request which
will be sent out soon.

thanks,
rui

> Regards
> Thara
> 
> > 
> > 
> >  drivers/thermal/thermal_sysfs.c | 11 +++++++----
> >  1 file changed, 7 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/thermal/thermal_sysfs.c
> > b/drivers/thermal/thermal_sysfs.c
> > index 2241cea..aa99edb 100644
> > --- a/drivers/thermal/thermal_sysfs.c
> > +++ b/drivers/thermal/thermal_sysfs.c
> > @@ -712,11 +712,14 @@ cur_state_store(struct device *dev, struct
> > device_attribute *attr,
> >  	if ((long)state < 0)
> >  		return -EINVAL;
> >  
> > +	mutex_lock(&cdev->lock);
> > +
> >  	result = cdev->ops->set_cur_state(cdev, state);
> > -	if (result)
> > -		return result;
> > -	thermal_cooling_device_stats_update(cdev, state);
> > -	return count;
> > +	if (!result)
> > +		thermal_cooling_device_stats_update(cdev, state);
> > +
> > +	mutex_unlock(&cdev->lock);
> > +	return result ? result : count;
> >  }
> >  
> >  static struct device_attribute
> > 
> 
> 

      reply	other threads:[~2019-01-03  2:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 22:43 [PATCH V2] thermal: Fix locking in cooling device sysfs update cur_state Thara Gopinath
2019-01-03  2:29 ` Thara Gopinath
2019-01-03  2:51   ` Zhang Rui [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=1546483882.2077.10.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=thara.gopinath@linaro.org \
    /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.