From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
nm@ti.com, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Dmitry Torokhov <dtor@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Len Brown <len.brown@intel.com>,
open list <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>, Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH V2 2/3] PM / OPP: Parse 'opp-supported-hw' binding
Date: Tue, 1 Dec 2015 12:22:52 +0530 [thread overview]
Message-ID: <20151201065252.GD4459@ubuntu> (raw)
In-Reply-To: <20151127044517.GU3869@ubuntu>
On 27-11-15, 10:15, Viresh Kumar wrote:
> > > + dev_opp->supported_hw = kmemdup(versions, count * sizeof(*versions),
> > > + GFP_KERNEL);
> >
> > And then we're going to modify said opp here under the mutex
> > lock.
>
> opp-dev ..
>
> > > + if (!dev_opp->supported_hw) {
> > > + ret = -ENOMEM;
> > > + goto err;
> > > + }
> > > +
> > > + dev_opp->supported_hw_count = count;
> >
> > So we've properly handled the concurrent writer case (which is
> > probably not even real), but we have improperly handled the case
> > where a reader is running in parallel to the writer. We should
> > only list_add_rcu the pointer once we're done modifying the
> > pointer we created. Otherwise a reader can come along and see the
> > half initialized structure, which is not good.
>
> This function will be called, from some platform code, before the OPP
> table is initialized. It isn't useful to call it after the OPPs are
> added for the device. So there wouldn't be any concurrent reader.
Since these functions are *only* going to be called before any OPPs
are added for the device, and hence ruling out any concurrent readers,
maybe we can guarantee that with this:
diff --git a/drivers/base/power/opp/core.c b/drivers/base/power/opp/core.c
index 5449bae74a44..ec74d98afe75 100644
--- a/drivers/base/power/opp/core.c
+++ b/drivers/base/power/opp/core.c
@@ -876,6 +876,9 @@ int dev_pm_opp_set_supported_hw(struct device *dev, const u32 *versions,
goto err;
}
+ /* Make sure there are no concurrent readers while updating dev_opp */
+ WARN_ON(!list_empty(&dev_opp->opp_list));
+
dev_opp->supported_hw = kmemdup(versions, count * sizeof(*versions),
GFP_KERNEL);
if (!dev_opp->supported_hw) {
@@ -924,6 +927,9 @@ void dev_pm_opp_put_supported_hw(struct device *dev)
goto unlock;
}
+ /* Make sure there are no concurrent readers while updating dev_opp */
+ WARN_ON(!list_empty(&dev_opp->opp_list));
+
if (!dev_opp->supported_hw) {
dev_err(dev, "%s: Doesn't have supported hardware list\n",
__func__);
I don't really want to create a duplicate dev_opp here and then
replace that in the list, because we know that we have just created
it.
Over that, if a reference to dev_opp is used somewhere else, lets say
within the pm_opp structure, then updating all OPPs at such times
would be really hard.
Lets close this before you go for vacations. I will get whatever
solution you feel is right.
--
viresh
next prev parent reply other threads:[~2015-12-01 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1447904566.git.viresh.kumar@linaro.org>
2015-11-19 3:43 ` [PATCH V2 1/3] PM / OPP: Add missing doc comments Viresh Kumar
2015-11-23 23:14 ` Rafael J. Wysocki
2015-11-19 3:43 ` [PATCH V2 2/3] PM / OPP: Parse 'opp-supported-hw' binding Viresh Kumar
2015-11-25 20:51 ` Stephen Boyd
2015-11-27 4:45 ` Viresh Kumar
2015-12-01 6:52 ` Viresh Kumar [this message]
2015-12-04 8:23 ` Viresh Kumar
2015-12-08 15:01 ` Viresh Kumar
2015-12-08 16:50 ` Rafael J. Wysocki
2015-12-08 16:31 ` Viresh Kumar
2015-12-09 1:15 ` Rafael J. Wysocki
2015-12-09 2:34 ` Viresh Kumar
2015-12-09 22:06 ` Rafael J. Wysocki
2015-11-19 3:43 ` [PATCH V2 3/3] PM / OPP: Parse 'opp-<prop>-<name>' bindings Viresh Kumar
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=20151201065252.GD4459@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=dtor@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=shawnguo@kernel.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