public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Gautham R Shenoy <ego@in.ibm.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-pm] pm-hibernate : possible circular locking dependency detected
Date: Mon, 6 Apr 2009 21:58:10 +0200	[thread overview]
Message-ID: <200904062158.11245.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0904061439230.4571-100000@iolanthe.rowland.org>

On Monday 06 April 2009, Alan Stern wrote:
> On Mon, 6 Apr 2009, Gautham R Shenoy wrote:
> 
> > > If I understand correctly it isn't really a deadlock scenario, but it
> > > is a lockdep violation.  The violation is:
> > > 
> > > 	The pci_device_probe() path 2) proves that dpm_list_mtx [4] can
> > > 	be acquired while cpu_hotplug.lock [3] is held;
> > > 
> > > 	The hibernate() path 3) proves that cpu_hotplug.lock [3] can be
> > > 	acquired while dpm_list_mtx [4] is held.
> > > 
> > > The two pathways cannot run simultaneously (and hence cannot deadlock) 
> > > because the prepare() stage of hibernation is supposed to stop all 
> > > device probing.  But lockdep will still report a problem.
> > 
> > Thanks for clarifying this Alan. I guess it boils down to teaching
> > lockdep about this false-positive.
> 
> Or else changing the code somehow to avoid the violation completely.  
> But I have no idea how...  And AFAIK, teaching lockdep about special 
> cases like this is not so easy to do.

Yeah, I've just wanted to ask about that.  Peter, how can we do it?

Rafael

  reply	other threads:[~2009-04-06 19:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05  9:53 pm-hibernate : possible circular locking dependency detected Ming Lei
2009-04-05 10:12 ` Rafael J. Wysocki
2009-04-05 13:44   ` Ingo Molnar
2009-04-06  0:55     ` Gautham R Shenoy
2009-04-06 13:29       ` Rafael J. Wysocki
2009-04-06 14:24         ` Gautham R Shenoy
2009-04-06 15:25           ` Rafael J. Wysocki
2009-04-06 14:37         ` [linux-pm] " Alan Stern
2009-04-06 15:20           ` Gautham R Shenoy
2009-04-06 18:42             ` Alan Stern
2009-04-06 19:58               ` Rafael J. Wysocki [this message]
2009-04-07  8:43                 ` Peter Zijlstra
2009-04-07  4:26     ` Rusty Russell
2009-04-07  7:05       ` Peter Zijlstra
2009-04-08  3:17         ` Rusty Russell
2009-04-08 12:26           ` Ingo Molnar
2009-04-08 12:48           ` Peter Zijlstra
2009-04-08 23:45             ` Rusty Russell
2009-04-09  4:17               ` Ingo Molnar
2009-04-09 14:45                 ` Ming Lei

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=200904062158.11245.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=ego@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --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