All of lore.kernel.org
 help / color / mirror / Atom feed
From: poma <pomidorabelisima@gmail.com>
To: David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <cl@linux.com>, Josh Boyer <jwboyer@redhat.com>,
	"Justin M. Forbes" <jforbes@redhat.com>,
	Dave Jones <davej@redhat.com>,
	kernel@lists.fedoraproject.org, linux-kernel@vger.kernel.org
Subject: Re: WARNING: CPU: 0 PID: 2243 at mm/slub.c:1007 deactivate_slab+0x4e0/0x590()
Date: Mon, 10 Feb 2014 13:40:43 +0100	[thread overview]
Message-ID: <52F8C8CB.1040204@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402100212280.30650@chino.kir.corp.google.com>

On 10.02.2014 11:14, David Rientjes wrote:
> On Mon, 10 Feb 2014, poma wrote:
> 
>> [   83.530421] WARNING: CPU: 0 PID: 2243 at mm/slub.c:1007
>> deactivate_slab+0x4e0/0x590()
> 
> Yeah, you'll need the patch from the http://marc.info/?t=139145791300002 
> thread.  It's in the -mm tree as
> mm-slub-list_lock-may-not-be-held-in-some-circumstances.patch and I'm 
> hoping it will go into 3.14-rc3, several people have been complaining 
> about it.
> 

All right!
Thanks for the prompt reply!

http://marc.info/?l=linux-kernel&m=139145999324131&q=raw
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/patch/mm/slub.c?id=aee03fe7a7c8c71540613b6918f766556bda40a7

Patched & tested with 3.14.0-0.rc1.git5.5.fc21.1.x86_64,
PASSED.


poma


      reply	other threads:[~2014-02-10 12:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10  2:00 WARNING: CPU: 0 PID: 2243 at mm/slub.c:1007 deactivate_slab+0x4e0/0x590() poma
2014-02-10 10:14 ` David Rientjes
2014-02-10 12:40   ` poma [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=52F8C8CB.1040204@gmail.com \
    --to=pomidorabelisima@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=davej@redhat.com \
    --cc=jforbes@redhat.com \
    --cc=jwboyer@redhat.com \
    --cc=kernel@lists.fedoraproject.org \
    --cc=linux-kernel@vger.kernel.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.