[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140625012640.GC29373@js1304-P5Q-DELUXE>
Date: Wed, 25 Jun 2014 10:26:40 +0900
From: Joonsoo Kim <iamjoonsoo.kim@....com>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: ak@...ux.intel.com, penberg@....fi, linux-kernel@...r.kernel.org
Subject: Re: [3.15-rc1 slab] Oops when reading /proc/slab_allocators
On Mon, Jun 23, 2014 at 07:59:17PM +0900, Tetsuo Handa wrote:
> Joonsoo Kim wrote:
> > On Thu, Apr 10, 2014 at 08:54:37PM +0900, Tetsuo Handa wrote:
> > > Joonsoo Kim wrote:
> > > > There was another report about this problem and I have already fixed
> > > > it, although it wasn't reviewed and merged. See following link.
> > > >
> > > > https://lkml.org/lkml/2014/3/11/119
> > >
> > > OK. That patch fixes this problem.
> > >
> > > Commit b1cb0982 changed the way of walking objects, didn't it? Then,
> > > it could happen that slab leak detector code walking all objects
> > > triggers an oops.
> >
> > Yeah, although it doesn't walks all objects, it walks non-active
> > objects and it is problematic. This behaviour comes from my patches :)
> >
> > >
> > > > In that time, I thought that this problem wasn't related to my patches,
> > > > but your bisect report say that it is from my patches. I will dig into
> > > > the problem more deeply as soon as possible and make proper fix.
> > >
> > > I see. Here is a minimal kernel config and test script for qemu on CentOS 6.5.
> > > http://I-love.SAKURA.ne.jp/tmp/config-pre-3.15-rc1-min
> >
> > Thanks.
> > I already sent another patch to fix this bug and cc'ed you.
> >
> > Thanks.
> >
>
> Hello.
>
> I noticed that 3.16-rc2 shows the same bug.
> Did you merge your patch for this bug into 3.15?
Hello,
I'm afriad of not.
It is merged yesterday, so it will appear on 3.16-rc3.
Sorry for late.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists