From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Hugh Dickins <hugh@veritas.com>,
linux-mm@kvack.org
Subject: Re: 2.6.28-rc2-mm1: possible circular locking
Date: Wed, 29 Oct 2008 14:54:46 -0700 [thread overview]
Message-ID: <20081029145446.081141b4@infradead.org> (raw)
In-Reply-To: <20081029135840.0a50e19c.akpm@linux-foundation.org>
On Wed, 29 Oct 2008 13:58:40 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> We've been calling schedule_on_each_cpu() from within
> lru_add_drain_all() for ages. What changed to cause all this
> to start happening?
what started to get these out of the weed is that copy_*_user() is now
annotated to (potentially) take the mmap sem (which it does if there's
a fault)...
previously you had to actually fault to get the lock dependency noticed.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit atty://www.lesswatts.org
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-10-29 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081028233836.8b1ff9ae.akpm@linux-foundation.org>
[not found] ` <200810292146.03967.m.kozlowski@tuxland.pl>
2008-10-29 20:58 ` Andrew Morton
2008-10-29 21:54 ` Arjan van de Ven [this message]
2008-10-31 3:21 ` KOSAKI Motohiro
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=20081029145446.081141b4@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hugh@veritas.com \
--cc=kernel-testers@vger.kernel.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.kozlowski@tuxland.pl \
--cc=nickpiggin@yahoo.com.au \
/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