linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Waiman Long <longman@redhat.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 2/2] cpufreq: Fix a circular lock dependency problem
Date: Tue, 24 Jul 2018 10:31:35 +0200	[thread overview]
Message-ID: <CAJZ5v0hbpk4FJQ3m4HCj_X44Jjp1JM21hwAAeisALmJQb8Cyfw@mail.gmail.com> (raw)
In-Reply-To: <20180723191627.GJ2494@hirez.programming.kicks-ass.net>

On Mon, Jul 23, 2018 at 9:16 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Jul 23, 2018 at 01:49:39PM -0400, Waiman Long wrote:
>>  drivers/cpufreq/cpufreq.c | 16 +++++++++++++++-
>>  1 file changed, 15 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>> index b0dfd32..9cf02d7 100644
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -922,8 +922,22 @@ static ssize_t store(struct kobject *kobj, struct attribute *attr,
>>       struct cpufreq_policy *policy = to_policy(kobj);
>>       struct freq_attr *fattr = to_attr(attr);
>>       ssize_t ret = -EINVAL;
>> +     int retries = 3;
>>
>> -     cpus_read_lock();
>> +     /*
>> +      * cpus_read_trylock() is used here to work around a circular lock
>> +      * dependency problem with respect to the cpufreq_register_driver().
>> +      * With a simple retry loop, the chance of not able to get the
>> +      * read lock is extremely small.
>> +      */
>> +     while (!cpus_read_trylock()) {
>> +             if (retries-- <= 0)
>> +                     return -EBUSY;
>> +             /*
>> +              * Sleep for about 50ms and retry again.
>> +              */
>> +             msleep(50);
>> +     }
>
> That's atrocious.

Agreed.

      parent reply	other threads:[~2018-07-24  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 17:49 [PATCH 0/2] cpufreq: Fix a circular lock dependency problem Waiman Long
2018-07-23 17:49 ` [PATCH 1/2] cpu/hotplug: Add a cpus_read_trylock() function Waiman Long
2018-07-23 17:49 ` [PATCH 2/2] cpufreq: Fix a circular lock dependency problem Waiman Long
2018-07-23 19:16   ` Peter Zijlstra
2018-07-23 19:27     ` Waiman Long
2018-07-24  8:36       ` Rafael J. Wysocki
2018-07-24  8:31     ` Rafael J. Wysocki [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=CAJZ5v0hbpk4FJQ3m4HCj_X44Jjp1JM21hwAAeisALmJQb8Cyfw@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).