From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com,
Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
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: Fri, 31 Oct 2008 12:21:16 +0900 (JST) [thread overview]
Message-ID: <20081031121827.AACB.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20081029135840.0a50e19c.akpm@linux-foundation.org>
> > stack backtrace:
> > Pid: 4733, comm: psi Not tainted 2.6.28-rc2-mm1 #1
> > Call Trace:
> > [<c013a0fd>] print_circular_bug_tail+0x78/0xb5
> > [<c0137a31>] ? print_circular_bug_entry+0x43/0x4b
> > [<c013a6e4>] validate_chain+0x5aa/0xfe0
> > [<c0118465>] ? hrtick_update+0x23/0x25
> > [<c013b388>] __lock_acquire+0x26e/0x98d
> > [<c0118ac0>] ? default_wake_function+0xb/0xd
> > [<c013bb03>] lock_acquire+0x5c/0x74
> > [<c012a330>] ? flush_work+0x2d/0xcb
> > [<c012a35c>] flush_work+0x59/0xcb
> > [<c012a330>] ? flush_work+0x2d/0xcb
> > [<c0139ae6>] ? trace_hardirqs_on+0xb/0xd
> > [<c012a531>] ? __queue_work+0x26/0x2b
> > [<c012a58c>] ? queue_work_on+0x37/0x47
> > [<c014fda7>] ? lru_add_drain_per_cpu+0x0/0xa
> > [<c014fda7>] ? lru_add_drain_per_cpu+0x0/0xa
> > [<c012a7a6>] schedule_on_each_cpu+0x65/0x7f
> > [<c014fb7e>] lru_add_drain_all+0xd/0xf
> > [<c0157fb2>] __mlock_vma_pages_range+0x44/0x206
> > [<c0159438>] ? vma_adjust+0x17e/0x384
> > [<c015971f>] ? split_vma+0xe1/0xf7
> > [<c01582d1>] mlock_fixup+0x15d/0x1c9
> > [<c0158479>] do_mlock+0x96/0xc8
> > [<c02bcb2a>] ? down_write+0x42/0x68
> > [<c015860e>] sys_mlock+0xb2/0xb6
> > [<c0102f91>] sysenter_do_call+0x12/0x35
> >
>
> This is similar to the problem which
> mm-move-migrate_prep-out-from-under-mmap_sem.patch was supposed to fix.
>
> 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?
Agreed with there are the same problem.
please assign this bug to me.
--
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>
prev parent reply other threads:[~2008-10-31 3:21 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
2008-10-31 3:21 ` KOSAKI Motohiro [this message]
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=20081031121827.AACB.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--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=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