[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikgi38O3=MsVNc-X64PnLOFNktC_x9Y3vQ7CbD+@mail.gmail.com>
Date: Thu, 16 Sep 2010 14:56:50 -0700
From: Tony Luck <tony.luck@...el.com>
To: Phil Carmody <ext-phil.2.carmody@...ia.com>
Cc: "fenghua.yu@...el.com" <fenghua.yu@...el.com>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] ia64: possible module unwind table optimisation
On Wed, Sep 15, 2010 at 3:22 PM, Phil Carmody
<ext-phil.2.carmody@...ia.com> wrote:
> Turn on kmemleak, or anything else which repeatedly runs up the stack just
> for the fun of gathering backtraces. Kmemleak's what caused us to notice
> the issue in our ARM-based environment.
kmemleak needs CONFIG_STACKTRACE - which I haven't got around to putting
into ia64 yet. I dug up an earlier attempt at doing so, and turned on kmemleak,
but it crashes early in boot (before ever getting to my stack tracer)
in possibly
the first call to kmem_cache_alloc(). With SLUB the error is an unaligned
reference to 0xffffffffffffffff, with SLAB I get a NULL deref.
:-(
-Tony
--
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