From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: ak@linux.intel.com, penberg@iki.fi, linux-kernel@vger.kernel.org
Subject: Re: [3.15-rc1 slab] Oops when reading /proc/slab_allocators
Date: Wed, 16 Apr 2014 09:10:49 +0900 [thread overview]
Message-ID: <20140416001049.GC14564@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <201404102054.BJI60908.OOFVLQFOSFHMJt@I-love.SAKURA.ne.jp>
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.
next prev parent reply other threads:[~2014-04-16 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 11:36 Tetsuo Handa
2014-04-10 7:39 ` Joonsoo Kim
2014-04-10 11:54 ` Tetsuo Handa
2014-04-16 0:10 ` Joonsoo Kim [this message]
2014-06-23 10:59 ` Tetsuo Handa
2014-06-25 1:26 ` Joonsoo Kim
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=20140416001049.GC14564@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@iki.fi \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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®