From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Julie Sullivan <kernelmail.jms@gmail.com>
Cc: Christoph Lameter <cl@linux.com>,
Shaohua Li <shaohua.li@intel.com>,
Yong Zhang <yong.zhang0@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: INFO: possible recursive locking detected: get_partial_node() on 3.2-rc1
Date: Fri, 11 Nov 2011 11:22:11 -0800 [thread overview]
Message-ID: <20111111192211.GE2283@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAAVPGOPwKV12TqwU1DcxvJTW9dsmWNiNFg4ga7PzWNgQ2M=1RQ@mail.gmail.com>
On Fri, Nov 11, 2011 at 07:09:01PM +0000, Julie Sullivan wrote:
> It's probably moot now but FWIW I checked Shaohua's patch too and it
> got rid of the warning in my dmesg.
Thank you both for your testing efforts! Hopefully there will be
a more permanent fix soon.
Thanx, Paul
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-11-11 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111109090556.GA5949@zhy>
2011-11-10 23:35 ` INFO: possible recursive locking detected: get_partial_node() on 3.2-rc1 Julie Sullivan
2011-11-11 3:04 ` Shaohua Li
2011-11-11 4:42 ` Yong Zhang
2011-11-11 14:57 ` Christoph Lameter
2011-11-11 15:02 ` Christoph Lameter
2011-11-11 19:09 ` Julie Sullivan
2011-11-11 19:22 ` Paul E. McKenney [this message]
2011-11-14 5:34 ` Shaohua Li
2011-11-15 7:22 ` Yong Zhang
2011-11-15 18:49 ` Pekka Enberg
2011-11-15 16:02 ` Christoph Lameter
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=20111111192211.GE2283@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=kernelmail.jms@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
--cc=yong.zhang0@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).