On 16/09/10 23:56 +0200, ext Tony Luck wrote: > On Wed, Sep 15, 2010 at 3:22 PM, Phil Carmody > <ext-phil.2.carmody@xxxxxxxxx> 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. > > :-( This is a shame, but not a real problem in the context of my patch - you can't usefully optimise something that's seemingly almost never used. It can be filed in the cylindrical filing cabinet. Phil -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|