Re: Slab panic on 2.6.19-rc3-git5 (-git4 was OK)

[Martin J. Bligh]

> > I only skimmed through this briefly but it looks like due to
> > 52fd24ca1db3a741f144bbc229beefe044202cac __get_vm_area_node is passing
> > GFP_HIGHMEM to kmem_cache_alloc_node which is a no-no.
>
> I haven't been able to reproduce this, although I understand why it happens:
> vmalloc allocates memory with
>
> GFP_KERNEL | __GFP_HIGHMEM
>
> and with git5, the same flags are passed down to cache_alloc_refill, causing
> the BUG. The following patch against 2.6.19-rc3-git5 (also attached as
> attachment, as this mailer may mess up inline copying) should fix it.

Thanks for the patch ... but more worrying is how this got broken.
Wasn't the point of having the -mm tree that patches like this went
through it for testing, and we avoid breaking mainline? especially
this late in the -rc cycle.

M.
-
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/