linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Pekka Enberg <penberg@kernel.org>, linux-next@vger.kernel.org
Subject: Re: [BUG? -next] WARNING: at mm/slub.c:1511
Date: Thu, 16 Jan 2014 16:25:24 +0100	[thread overview]
Message-ID: <20140116152524.GC5660@osiris> (raw)
In-Reply-To: <20140116152203.GV30183@twins.programming.kicks-ass.net>

On Thu, Jan 16, 2014 at 04:22:03PM +0100, Peter Zijlstra wrote:
> On Thu, Jan 16, 2014 at 03:58:13PM +0100, Heiko Carstens wrote:
> > Hi Peter, Pekka,
> > 
> > the patch "slub: use lockdep_assert_held" reveals possible missing locking,
> > even though I don't think it will do any harm.
> > However somebody familar with slab/slub should have a look and fix this:
> > 
> Dave Hansen already send a fix for that:
> 
> lkml.kernel.org/r/52D5746F.2040604@intel.com

Ok, thanks for the pointer!

      reply	other threads:[~2014-01-16 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 14:58 [BUG? -next] WARNING: at mm/slub.c:1511 Heiko Carstens
2014-01-16 15:22 ` Peter Zijlstra
2014-01-16 15:25   ` Heiko Carstens [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=20140116152524.GC5660@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).