From: chenqiwu <qiwuchen55@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: f.fainelli@gmail.com, linux-pm@vger.kernel.org,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, mmayer@broadcom.com,
chenqiwu <chenqiwu@xiaomi.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] cpufreq: brcmstb-avs: fix imbalance of cpufreq policy refcount
Date: Mon, 20 Jan 2020 14:27:56 +0800 [thread overview]
Message-ID: <20200120062756.GA5802@cqw-OptiPlex-7050> (raw)
In-Reply-To: <20200120062126.nmxaqhcpqcojuihr@vireshk-i7>
On Mon, Jan 20, 2020 at 11:51:26AM +0530, Viresh Kumar wrote:
> On 20-01-20, 14:13, chenqiwu wrote:
> > On Mon, Jan 20, 2020 at 11:31:34AM +0530, Viresh Kumar wrote:
> > > On 20-01-20, 13:58, chenqiwu wrote:
> > > > On Mon, Jan 20, 2020 at 11:02:50AM +0530, Viresh Kumar wrote:
> > > > > On 19-01-20, 15:09, qiwuchen55@gmail.com wrote:
> > > > > > From: chenqiwu <chenqiwu@xiaomi.com>
> > > > > >
> > > > > > brcm_avs_cpufreq_get() calls cpufreq_cpu_get() to get the cpufreq policy,
> > > > > > 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.
> > > > > >
> > > > > > For fixing this bug, cpufreq_get_policy() is referenced to do a proper
> > > > > > cpufreq_cpu_get()/cpufreq_cpu_put() and fill a policy copy for the user.
> > > > > > If the policy return NULL, we just return 0 to hit the code path of
> > > > > > cpufreq_driver->get.
> > > > > >
> > > > > > Signed-off-by: chenqiwu <chenqiwu@xiaomi.com>
> > > > > > ---
> > > > > > drivers/cpufreq/brcmstb-avs-cpufreq.c | 12 ++++++++++--
> > > > > > 1 file changed, 10 insertions(+), 2 deletions(-)
> > > > > >
> > > > > > diff --git a/drivers/cpufreq/brcmstb-avs-cpufreq.c b/drivers/cpufreq/brcmstb-avs-cpufreq.c
> > > > > > index 77b0e5d..ee0d404 100644
> > > > > > --- a/drivers/cpufreq/brcmstb-avs-cpufreq.c
> > > > > > +++ b/drivers/cpufreq/brcmstb-avs-cpufreq.c
> > > > > > @@ -452,8 +452,16 @@ static bool brcm_avs_is_firmware_loaded(struct private_data *priv)
> > > > > >
> > > > > > static unsigned int brcm_avs_cpufreq_get(unsigned int cpu)
> > > > > > {
> > > > > > - struct cpufreq_policy *policy = cpufreq_cpu_get(cpu);
> > > > >
> > > > > Why can't we just add a corresponding cpufreq_cpu_put() instead of all this ?
> > > > >
> > > >
> > > > cpufreq_get_policy() does a proper cpufreq_cpu_get()/cpufreq_cpu_put(),
> > > > meanwhile fills a policy copy for the user. It equals to using
> > > > cpufreq_cpu_get() and a corresponding cpufreq_cpu_put() around access
> > > > to the policy pointer. I think both methods are fine here.
> > > > What do you think?
> > >
> > > cpufreq_get_policy() does an extra memcpy as well, which isn't required at all
> > > in your case.
> > >
> > > --
> > > viresh
> >
> > Huha..Do you worry about the race conditon with cpufreq policy free path?
>
> No. I just worry about an unnecessary memcpy, nothing else.
>
Is there any question about this extra memcpy?
Qiwu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-20 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 7:09 [PATCH v3] cpufreq: brcmstb-avs: fix imbalance of cpufreq policy refcount qiwuchen55
2020-01-20 5:32 ` Viresh Kumar
2020-01-20 5:58 ` chenqiwu
2020-01-20 6:01 ` Viresh Kumar
2020-01-20 6:13 ` chenqiwu
2020-01-20 6:21 ` Viresh Kumar
2020-01-20 6:27 ` chenqiwu [this message]
2020-01-20 6:30 ` Viresh Kumar
2020-01-20 6:50 ` 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=20200120062756.GA5802@cqw-OptiPlex-7050 \
--to=qiwuchen55@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chenqiwu@xiaomi.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox