Nick wrote:
> Kernel should not panic if a GFP_ATOMIC allocation fails.
> Where is this happening?
I didn't actually see any such panics occur. This patch came from
reading code, not any actual crash seen so far. The closest thing to a
real world event that I saw was a network connection that go
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
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.
Signed-
3 matches
Mail list logo
