Re: linux-next: Tree for July 11

From: Arjan van de Ven
Date: Sat Jul 12 2008 - 15:32:24 EST


On Sat, 12 Jul 2008 21:21:38 +0200
"Vegard Nossum" <vegard.nossum@xxxxxxxxx> wrote:

> > [<ffffffff8023d37f>] warn_on_slowpath+0x5f/0x80
> > [<ffffffff80220030>] ? hpet_unregister_irq_handler+0x0/0x30
> > [<ffffffff8022a8ae>] ? kmemcheck_mark_initialized+0xe/0x10
> > [<ffffffff802b97fb>] ? kmemcheck_slab_alloc+0x2b/0x50
> > [<ffffffff802b8610>] ? kmem_cache_alloc+0xc0/0x140
> > [<ffffffff80291921>] ? mempool_alloc_slab+0x11/0x20
> > [<ffffffff80291a8b>] ? mempool_alloc+0x5b/0x140
> > [<ffffffff803575db>] blk_plug_device+0x9b/0xb0
> > [<ffffffff80453d9f>] bitmap_startwrite+0xbf/0x1b0
> > [<ffffffff802e87e4>] ? bio_alloc_bioset+0x54/0xb0
> > [<ffffffffa004eafa>] make_request+0x39a/0x810 [raid1]
> > [<ffffffff80291a8b>] ? mempool_alloc+0x5b/0x140
> > [<ffffffff80291a8b>] ? mempool_alloc+0x5b/0x140
> > [<ffffffff8035682d>] generic_make_request+0x17d/0x2b0
> > [<ffffffff803581dc>] submit_bio+0x6c/0xf0
> Hm, even though there's kmemcheck in the stacktrace, I think it's
> unrelated. Probably it's just a call that returned and the addresses
> were left on the stack.

more than "probably".. that's what the "?" in the trace is for ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/