mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: dormando <dormando@rydia.net>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	netdev@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Alexei Starovoitov <ast@plumgrid.com>
Subject: Re: kmem_cache_alloc panic in 3.10+
Date: Fri, 31 Jan 2014 13:19:29 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1401311315110.27318@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1401301951060.5516@dinf>

On Thu, 30 Jan 2014, dormando wrote:

> > > I really wonder... it looks like a possible in SLUB. (might be already
> > > fixed)
> > >
> > > Could you try using SLAB instead ?
> >
> > try config_slub_debug_on=y ? it should catch double free and other things.
> >
> 
> Any slowdowns/issues with that?

CONFIG_SLUB_DEBUG_ON will definitely be slower but can help to identify 
any possible corruption issues.

I'm wondering if you have CONFIG_MEMCG enabled and are actually allocating 
slab in a non-root memcg?  What does /proc/self/cgroup say?

  reply	other threads:[~2014-01-31 21:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18  8:44 dormando
2014-01-18 16:29 ` Eric Dumazet
2014-01-18 16:57   ` Eric Dumazet
2014-01-18 19:03   ` dormando
2014-01-30  7:05     ` dormando
2014-01-31  2:16       ` Eric Dumazet
2014-01-31  3:46         ` Alexei Starovoitov
2014-01-31  3:52           ` dormando
2014-01-31 21:19             ` David Rientjes [this message]
2014-01-31 22:11               ` dormando
2014-01-31 23:22                 ` David Rientjes
2014-01-31 23:43                   ` dormando
2014-02-01  0:32                     ` Eric Dumazet

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.1401311315110.27318@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ast@plumgrid.com \
    --cc=dormando@rydia.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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

all inboxes | Powered by JetHome®