From: David Rientjes <rientjes@google.com>
To: Fengguang Wu <fengguang.wu@intel.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: Wed, 5 Feb 2014 11:25:35 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1402051123520.5616@chino.kir.corp.google.com> (raw)
In-Reply-To: <20140205112449.GB18849@localhost>
On Wed, 5 Feb 2014, Fengguang Wu wrote:
> > I think this is the inlined add_full() and should be fixed with
> > http://marc.info/?l=linux-kernel&m=139147105027693 that has been added to
> > the -mm tree and should now be in next. Is this patch included for this
> > kernel?
>
> Hi David,
>
> According to the bisect log, linux-next 20140204 is bad, but it does
> not yet include your fix.
>
> git bisect bad 38dbfb59d1175ef458d006556061adeaa8751b72 # 23:16 0- 2 Linus 3.14-rc1
> git bisect bad cdd263faccc2184e685573968dae5dd34758e322 # 23:34 1- 3 Add linux-next specific files for 20140204
>
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.
--
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:[~2014-02-05 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 7:25 Fengguang Wu
2014-02-05 8:10 ` David Rientjes
2014-02-05 11:24 ` Fengguang Wu
2014-02-05 19:25 ` David Rientjes [this message]
2014-02-06 21:41 ` David Rientjes
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=alpine.DEB.2.02.1402051123520.5616@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
/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