From: ebiederm@xmission.com (Eric W. Biederman)
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
Miles Lane <miles.lane@gmail.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
akpm@linux-foundation.org
Subject: Re: [Patch v2] sysfs: add lockdep class support to s_active
Date: Fri, 05 Feb 2010 01:01:47 -0800 [thread overview]
Message-ID: <m1iqachx8k.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20100205064622.4141.72867.sendpatchset@localhost.localdomain> (Amerigo Wang's message of "Fri\, 5 Feb 2010 01\:42\:56 -0500")
Amerigo Wang <amwang@redhat.com> writes:
> Recently we met a lockdep warning from sysfs during s2ram or cpu hotplug.
> As reported by several people, it is something like:
The interesting case is the cpu hotplug is actually a problem. It isn't
useful to get a complaint about the non-problems code paths triggered
by pm. However my earlier review spotted a real deadlock case. Where
in one of the sysfs attributes we iterate over the list of online cpus
and that appeared to an attribute that removing a cpu would remove
from sysfs...
Eric
next prev parent reply other threads:[~2010-02-05 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 6:42 [Patch v2] sysfs: add lockdep class support to s_active Amerigo Wang
2010-02-05 7:09 ` Xiaotian Feng
2010-02-05 7:27 ` Cong Wang
2010-02-05 9:39 ` Eric W. Biederman
2010-02-05 9:48 ` Cong Wang
2010-02-05 10:00 ` Xiaotian Feng
2010-02-08 3:12 ` Cong Wang
2010-02-05 8:57 ` Eric W. Biederman
2010-02-05 9:29 ` Cong Wang
2010-02-05 9:01 ` Eric W. Biederman [this message]
2010-02-05 9:37 ` Cong Wang
2010-02-05 9:59 ` Eric W. Biederman
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=m1iqachx8k.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=Larry.Finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=gregkh@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=peterz@infradead.org \
--cc=tj@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 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.