From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH] PM: runtime: fix recursive locking warning of lockdep from rpm_resume
Date: Fri, 22 Oct 2010 23:50:14 +0200 [thread overview]
Message-ID: <201010222350.14480.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1010221024140.1529-100000@iolanthe.rowland.org>
On Friday, October 22, 2010, Alan Stern wrote:
> On Fri, 22 Oct 2010 tom.leiming@gmail.com wrote:
>
> > From: Ming Lei <tom.leiming@gmail.com>
> >
> > For device with no_callbacks flag set, its power lock and its parent's
> > power lock may be held nestedly in rpm_resume, so we should take
> > spin_lock_nested(lock, SINGLE_DEPTH_NESTING) to acquire parent power lock
> > to avoid lockdep warning.
> >
> > Signed-off-by: Ming Lei <tom.leiming@gmail.com>
> > ---
> > drivers/base/power/runtime.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c
> > index 1dd8676..126ca49 100644
> > --- a/drivers/base/power/runtime.c
> > +++ b/drivers/base/power/runtime.c
> > @@ -503,7 +503,7 @@ static int rpm_resume(struct device *dev, int rpmflags)
> > * the resume will actually succeed.
> > */
> > if (dev->power.no_callbacks && !parent && dev->parent) {
> > - spin_lock(&dev->parent->power.lock);
> > + spin_lock_nested(&dev->parent->power.lock, SINGLE_DEPTH_NESTING);
> > if (dev->parent->power.disable_depth > 0
> > || dev->parent->power.ignore_children
> > || dev->parent->power.runtime_status == RPM_ACTIVE) {
>
> Quite correct; I don't know why this didn't show up during my testing.
>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
Applied to suspend-2.6/pm-fixes, will push to Linus early next week.
Thanks,
Rafael
prev parent reply other threads:[~2010-10-22 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 11:58 [PATCH] PM: runtime: fix recursive locking warning of lockdep from rpm_resume tom.leiming
2010-10-22 14:25 ` Alan Stern
2010-10-22 21:50 ` 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=201010222350.14480.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
/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