From: Fengguang Wu <fengguang.wu@intel.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [slub] WARNING: CPU: 1 PID: 1 at mm/slub.c:992 deactivate_slab()
Date: Fri, 7 Feb 2014 10:46:02 +0800 [thread overview]
Message-ID: <20140207024602.GA12062@localhost> (raw)
In-Reply-To: <alpine.DEB.2.02.1402061340360.12761@chino.kir.corp.google.com>
On Thu, Feb 06, 2014 at 01:41:10PM -0800, David Rientjes wrote:
> On Wed, 5 Feb 2014, David Rientjes wrote:
>
> > Ah, that's because the patch didn't go through Pekka's slab tree but went
> > into -mm instead so we have to wait for another -mm. However, the traces
> > from linux-next-20140204 that you provided indicate it's the same problem
> > and should be fixed with that patch, so let's wait for another mmotm to be
> > released.
> >
>
> Ok, "mm/slub.c: list_lock may not be held in some circumstances" is in
> linux-next so let me know if this reproduces!
Yeah, linux-next 20140206 no longer has this WARNING!
Thanks,
Fengguang
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [slub] WARNING: CPU: 1 PID: 1 at mm/slub.c:992 deactivate_slab()
Date: Fri, 7 Feb 2014 10:46:02 +0800 [thread overview]
Message-ID: <20140207024602.GA12062@localhost> (raw)
In-Reply-To: <alpine.DEB.2.02.1402061340360.12761@chino.kir.corp.google.com>
On Thu, Feb 06, 2014 at 01:41:10PM -0800, David Rientjes wrote:
> On Wed, 5 Feb 2014, David Rientjes wrote:
>
> > Ah, that's because the patch didn't go through Pekka's slab tree but went
> > into -mm instead so we have to wait for another -mm. However, the traces
> > from linux-next-20140204 that you provided indicate it's the same problem
> > and should be fixed with that patch, so let's wait for another mmotm to be
> > released.
> >
>
> Ok, "mm/slub.c: list_lock may not be held in some circumstances" is in
> linux-next so let me know if this reproduces!
Yeah, linux-next 20140206 no longer has this WARNING!
Thanks,
Fengguang
next prev parent reply other threads:[~2014-02-07 2:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 7:25 [slub] WARNING: CPU: 1 PID: 1 at mm/slub.c:992 deactivate_slab() Fengguang Wu
2014-02-05 8:10 ` David Rientjes
2014-02-05 8:10 ` David Rientjes
2014-02-05 11:24 ` Fengguang Wu
2014-02-05 11:24 ` Fengguang Wu
2014-02-05 19:25 ` David Rientjes
2014-02-05 19:25 ` David Rientjes
2014-02-06 21:41 ` David Rientjes
2014-02-06 21:41 ` David Rientjes
2014-02-07 2:46 ` Fengguang Wu [this message]
2014-02-07 2:46 ` Fengguang Wu
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=20140207024602.GA12062@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.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 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.