From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: kosaki.motohiro@jp.fujitsu.com,
Minchan Kim <minchan.kim@gmail.com>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Nick Piggin <npiggin@suse.de>
Subject: Re: kernel BUG at mm/slqb.c:1411!
Date: Thu, 14 May 2009 17:54:29 +0900 (JST) [thread overview]
Message-ID: <20090514175332.9B7B.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1242289830.21646.5.camel@penberg-laptop>
> On Wed, 2009-05-13 at 17:37 +0900, Minchan Kim wrote:
> > On Wed, 13 May 2009 16:42:37 +0900 (JST)
> > KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> >
> > Hmm. I don't know slqb well.
> > So, It's just my guess.
> >
> > We surely increase l->nr_partial in __slab_alloc_page.
> > In between l->nr_partial++ and call __cache_list_get_page, Who is decrease l->nr_partial again.
> > After all, __cache_list_get_page return NULL and hit the VM_BUG_ON.
> >
> > Comment said :
> >
> > /* Protects nr_partial, nr_slabs, and partial */
> > spinlock_t page_lock;
> >
> > As comment is right, We have to hold the l->page_lock ?
>
> Makes sense. Nick? Motohiro-san, can you try this patch please?
This issue is very rarely. please give me one night.
--
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:[~2009-05-14 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 7:42 KOSAKI Motohiro
2009-05-13 8:37 ` Minchan Kim
2009-05-14 8:30 ` Pekka Enberg
2009-05-14 8:54 ` KOSAKI Motohiro [this message]
2009-05-14 23:38 ` KOSAKI Motohiro
2009-05-15 8:08 ` Pekka Enberg
2009-05-15 15:21 ` KOSAKI Motohiro
2009-05-25 11:12 ` Nick Piggin
2009-05-14 8:23 ` Pekka Enberg
2009-05-14 8:27 ` 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=20090514175332.9B7B.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
/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