From: Viresh Kumar <viresh.kumar@linaro.org>
To: qiwuchen55@gmail.com
Cc: kgene@kernel.org, krzk@kernel.org, rjw@rjwysocki.net,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
chenqiwu <chenqiwu@xiaomi.com>
Subject: Re: [PATCH v3] cpufreq: s3c: fix unbalances of cpufreq policy refcount
Date: Tue, 7 Jan 2020 13:31:45 +0530 [thread overview]
Message-ID: <20200107080145.7c4gxilnjjxjfqpc@vireshk-i7> (raw)
In-Reply-To: <1578383599-11207-1-git-send-email-qiwuchen55@gmail.com>
On 07-01-20, 15:53, qiwuchen55@gmail.com wrote:
> From: chenqiwu <chenqiwu@xiaomi.com>
>
> The cpufreq_reboot_notifier_evt() call cpufreq_cpu_get() to get the
> cpufreq policy of cpu0, meanwhile, it also increments the kobject
> reference count to mark it busy. However, a corresponding call of
> cpufreq_cpu_put() is ignored to decrement the kobject reference count
> back, which may lead to a potential stuck risk that the cpuhp thread
> deadly waits for dropping of kobject refcount when cpufreq policy free.
>
> With this patch, the cpuhp thread can be easily exercised by attempting
> to force an unbind of the CPUfreq driver.
>
> Signed-off-by: chenqiwu <chenqiwu@xiaomi.com>
> ---
> changes in v3:
> - Rewrite title and commit message.
> ---
> drivers/cpufreq/s3c2416-cpufreq.c | 12 +++++++++++-
> drivers/cpufreq/s5pv210-cpufreq.c | 11 ++++++++++-
> 2 files changed, 21 insertions(+), 2 deletions(-)
Applied. Thanks.
--
viresh
next prev parent reply other threads:[~2020-01-07 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 7:53 [PATCH v3] cpufreq: s3c: fix unbalances of cpufreq policy refcount qiwuchen55
2020-01-07 8:01 ` Viresh Kumar [this message]
[not found] ` <CAD1-QrohtJFLWDMCYmVs2G5WDcDN_E8xcsNZqJ428cEkohcB0Q@mail.gmail.com>
2020-01-20 5:28 ` Viresh Kumar
2020-01-20 5:43 ` chenqiwu
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=20200107080145.7c4gxilnjjxjfqpc@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=chenqiwu@xiaomi.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=qiwuchen55@gmail.com \
--cc=rjw@rjwysocki.net \
/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).