On 02/19/2013 01:29 PM, Dave Jones wrote:
> 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.
It happened once on a kernel built on my gentoo box with is generally up to
date,
but the other time the kernel was built on my mini-server running ubuntu, which
isn't updated that often.
So I don't think compiler trickery is involved.
Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
