From: dormando <dormando@rydia.net>
To: David Rientjes <rientjes@google.com>
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 15:43:43 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1401311537290.17834@dtop> (raw)
In-Reply-To: <alpine.DEB.2.02.1401311521170.18890@chino.kir.corp.google.com>
On Fri, 31 Jan 2014, David Rientjes wrote:
> On Fri, 31 Jan 2014, dormando wrote:
>
> > > 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?
> > >
> >
> > /proc/self/cgroup is empty on these hosts. CONFIG_MEMCG is enabled though.
> >
>
> It _looks_ like the cmpxchg_double() so seeing if there is anything else
> funny going on with CONFIG_SLUB_DEBUG_ON would definitely be helpful;
> otherwise, try using CONFIG_SLAB is Eric suggested and seeing if the
> problem goes away.
>
chpxchg_double()? that's not related to the 62713c4b fix right?
I'll see what I can do.. it's going to take a long time to iterate on this
though.
Thanks for the suggestions!
next prev parent reply other threads:[~2014-01-31 23:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 8:44 kmem_cache_alloc panic in 3.10+ 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
2014-01-31 22:11 ` dormando
2014-01-31 23:22 ` David Rientjes
2014-01-31 23:43 ` dormando [this message]
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.1401311537290.17834@dtop \
--to=dormando@rydia.net \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@plumgrid.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox