Re: [patch] mm, oom: do not schedule if current has been killed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 19 Jun 2012, Kamezawa Hiroyuki wrote:

> fatal_signal_pending() == false if test_thread_flag(TIF_MEMDIE)==false ?
> 

Yeah, the only thing that sets TIF_MEMDIE is the oom killer and it 
immediately SIGKILLs it afterwards.

Aside: I've been thinking of adding a check to the page allocator for 
!(gfp & __GFP_FS) && !(gfp & __GFP_NORETRY) to set TIF_MEMDIE for current 
if it has a fatal signal since such an allocation isn't eligible for 
calling into the oom killer.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]