mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aaro Koskinen <aaro.koskinen@nokia.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 4.3-rc7: kmemleak BUG: Redzone overwritten
Date: Tue, 27 Oct 2015 18:06:50 +0200	[thread overview]
Message-ID: <20151027160650.GW1284@ak-desktop.emea.nsn-net.net> (raw)
In-Reply-To: <1445961371.6332.36.camel@linux.intel.com>

Hi,

On Tue, Oct 27, 2015 at 05:56:11PM +0200, Andy Shevchenko wrote:
> On Tue, 2015-10-27 at 17:46 +0200, Aaro Koskinen wrote:
> > With 4.3-rc7 and slub_debug=FZUP, I get the below when reading
> > /sys/kernel/debug/kmemleak with a large number of reported entries.
> > It's pretty repeatable. HW is MIPS64.
> > 
> > With the SLUB debugging disabled, box crashes randomly in
> > kmem_cache_free
> > or kmem_cache_alloc when the kmemleak file is read on a running
> > system.
> > 
> > Seems to start with 6fc37c490076 ("kmemleak: use seq_hex_dump() to
> > dump buffers").
> 
> So, you mean reverting it does help?

Yes.

> Btw, we have kmemleak test suite. Any suggestion how can it be
> reproducible with it?

Maybe a add test for big number of objects? In this case there are 3072
reported objects.

A.

  reply	other threads:[~2015-10-27 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 15:46 Aaro Koskinen
2015-10-27 15:56 ` Andy Shevchenko
2015-10-27 16:06   ` Aaro Koskinen [this message]
2015-10-27 22:16 ` Linus Torvalds
2015-10-27 22:39   ` Andy Shevchenko
2015-10-27 22:43     ` Linus Torvalds

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=20151027160650.GW1284@ak-desktop.emea.nsn-net.net \
    --to=aaro.koskinen@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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®