All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-pm <linux-pm@lists.osdl.org>
Subject: Re: Re: lockdep report in hibernate code
Date: Wed, 24 Oct 2007 14:57:15 -0700	[thread overview]
Message-ID: <20071024215715.GA9524@kroah.com> (raw)
In-Reply-To: <1193215220.4097.8.camel@johannes.berg>

On Wed, Oct 24, 2007 at 10:40:20AM +0200, Johannes Berg wrote:
> On Wed, 2007-10-24 at 00:18 +0200, Rafael J. Wysocki wrote:
> 
> > Yes, which is what I think is happening in this particular case.  More
> > precisely, we get pm_mutex while holding a buffer mutex, so lockdep is warning
> > when we get another buffer mutex afterwards.
> 
> Precisely. That's why I copied Greg on the second mail :) It seems that
> sysfs already uses nested locks, but that only protects against lockdep
> reporting a false positive for nested locks, not this case.

Ok, I'm confused, where is the sysfs issue here?

thanks,

greg k-h

  reply	other threads:[~2007-10-24 21:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 14:11 lockdep report in hibernate code Johannes Berg
2007-10-22 22:39 ` Rafael J. Wysocki
2007-10-23 10:34   ` Johannes Berg
2007-10-23 21:39     ` Rafael J. Wysocki
2007-10-23 21:56       ` Alan Stern
2007-10-23 22:18         ` Rafael J. Wysocki
2007-10-24  8:40           ` Johannes Berg
2007-10-24 21:57             ` Greg KH [this message]
2007-10-25 13:31               ` Johannes Berg
2007-10-25 17:13                 ` Alan Stern
2007-10-26 10:36                   ` Johannes Berg
2007-10-27 22:29                     ` Alan Stern
2007-10-28 10:38                       ` Johannes Berg

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=20071024215715.GA9524@kroah.com \
    --to=greg@kroah.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-pm@lists.osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.