Re: [PATCH 2.6.12-rc1] cpusets special case GFP_ATOMIC allocs

[Nick Piggin]

Paul Jackson wrote:
> Stringent enforcement of cpuset memory placement could cause
> the kernel to panic on a GFP_ATOMIC (!wait) memory allocation,
> even though memory was available elsewhere in the system.
>
> Relax the cpuset constraint, on the last zone loop in
> mm/page_alloc.c:__alloc_pages(), for ATOMIC requests.

Kernel should not panic if a GFP_ATOMIC allocation fails.
Where is this happening?

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