From: Nishanth Menon <nm@ti.com>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: <myungjoo.ham@samsung.com>, <kyungmin.park@samsung.com>,
<yongjun_wei@trendmicro.com.cn>, <linux-kernel@vger.kernel.org>,
<rjw@sisk.pl>
Subject: Re: [PATCH] PM / devfreq: fix missing unlock on error in exynos4_busfreq_pm_notifier_event()
Date: Thu, 21 Feb 2013 22:49:17 -0600 [thread overview]
Message-ID: <20130222044917.GA24752@kahuna> (raw)
In-Reply-To: <CAPgLHd-xToKRxXtknB0O3DZnaqEAqJ4cXpV_HHnJNs0Gx9OVPA@mail.gmail.com>
On 12:33-20130222, Wei Yongjun wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> Add the missing unlock before return from function
> exynos4_busfreq_pm_notifier_event() in the error
> handling case.
>
> This issue introduced by commit 8fa938
> (PM / devfreq: exynos4_bus: honor RCU lock usage)
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> ---
> drivers/devfreq/exynos4_bus.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/devfreq/exynos4_bus.c b/drivers/devfreq/exynos4_bus.c
> index 46d94e9..6208a68 100644
> --- a/drivers/devfreq/exynos4_bus.c
> +++ b/drivers/devfreq/exynos4_bus.c
> @@ -974,6 +974,7 @@ static int exynos4_busfreq_pm_notifier_event(struct notifier_block *this,
> rcu_read_unlock();
> dev_err(data->dev, "%s: unable to find a min freq\n",
> __func__);
> + mutex_unlock(&data->lock);
> return PTR_ERR(opp);
> }
> new_oppinfo.rate = opp_get_freq(opp);
>
>
Arrgh.. Thanks for catching this :( My bad.
Fix looks good to me. upto MyungJoo.
MyungJoo, Rafael,
btw, adding linux-pm@vger.kernel.org to MAINTAINERS for devfreq might
be a nice idea to have right audience.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-02-22 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 4:33 Wei Yongjun
2013-02-22 4:49 ` Nishanth Menon [this message]
2013-02-22 6:33 MyungJoo Ham
2013-02-22 12:41 ` Rafael J. Wysocki
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=20130222044917.GA24752@kahuna \
--to=nm@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@sisk.pl \
--cc=weiyj.lk@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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
all inboxes | Powered by JetHome®