From: Dave Jones <davej@redhat.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
mpm@selenic.com, linux-mm <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: slab: odd BUG on kzalloc
Date: Tue, 19 Feb 2013 13:29:52 -0500 [thread overview]
Message-ID: <20130219182952.GB27141@redhat.com> (raw)
In-Reply-To: <5123C1F1.6050102@oracle.com>
On Tue, Feb 19, 2013 at 01:18:25PM -0500, Sasha Levin wrote:
> >> [ 169.930103] ---[ end trace 4d135f3def21b4bd ]---
> >>
> >> The code translates to the following in fs/pipe.c:alloc_pipe_info :
> >>
> >> pipe = kzalloc(sizeof(struct pipe_inode_info), GFP_KERNEL);
> >> if (pipe) {
> >> pipe->bufs = kzalloc(sizeof(struct pipe_buffer) * PIPE_DEF_BUFFERS, GFP_KERNEL); <=== this
> >> if (pipe->bufs) {
> >> init_waitqueue_head(&pipe->wait);
>
> Looks like it's not specific to pipe(). I've also got this one now:
>
> Since I've managed to reproduce it, I'll go ahead and add slub_debug and see what it tells us.
I'm curious, did you recently upgrade gcc, or other parts of the toolchain ?
This, and one of the other 'weird' bugs you reported recently have me wondering
if perhaps you're seeing a compiler bug.
Dave
--
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:[~2013-02-19 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 15:56 slab: odd BUG on kzalloc Sasha Levin
2013-02-19 0:35 ` Christoph Lameter
2013-02-19 18:18 ` Sasha Levin
2013-02-19 18:29 ` Dave Jones [this message]
2013-02-19 18:32 ` Sasha Levin
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=20130219182952.GB27141@redhat.com \
--to=davej@redhat.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=sasha.levin@oracle.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;
as well as URLs for NNTP newsgroup(s).