Re: CONFIG_SLAB_DEBUG and NUMA API
From: R. J. Wysocki (rjwysocki_at_sisk.pl)
Date: 07/07/04
- Previous message: Povolotsky, Alexander: "RE: Maximum frequency of re-scheduling (minimum time quantum) que stio n"
- In reply to: Andi Kleen: "Re: CONFIG_SLAB_DEBUG and NUMA API"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Andi Kleen <ak@muc.de>, Andrew Morton <akpm@osdl.org> Date: Wed, 7 Jul 2004 10:10:59 +0200
On Tuesday 06 of July 2004 23:03, Andi Kleen wrote:
> On Mon, Jul 05, 2004 at 11:49:45PM -0700, Andrew Morton wrote:
> > Andi Kleen <ak@muc.de> wrote:
> > > I tested 2.6.7-mm6 with NUMA on with CONFIG_SLAB_DEBUG and I didn't see
> > > any oopses. Do you have a recipe to reproduce them?
> >
> > Still happens here. Booting SLES9.1 with the attached config.
>
> [...]
>
> Here's a patch. The problem was that the kernel exit would allocate
> memory to send exit signals after the local mempolicy was already freed,
> but not zeroed. When the allocator tried to grab more memory it would
> fall over.
>
> -Andi
>
> -------------------------------------------------------------
>
> Move the memory policy freeing to later in exit to make sure
> the last memory allocations don't use an uninitialized policy
It fixed the problems that I had reported on both 2.6.7-mm6 and 2.6.7-bk18.
Thanks a lot,
rjw
-- Rafael J. Wysocki ---------------------------- For a successful technology, reality must take precedence over public relations, for nature cannot be fooled. -- Richard P. Feynman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Povolotsky, Alexander: "RE: Maximum frequency of re-scheduling (minimum time quantum) que stio n"
- In reply to: Andi Kleen: "Re: CONFIG_SLAB_DEBUG and NUMA API"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
