On Tue, 27 Sep 2011, Michal Hocko wrote: > I guess you mean a situation when select_bad_process picks up a process > which is not marked as frozen yet but we send SIGKILL right before > schedule is called in refrigerator. > In that case either schedule should catch it by signal_pending_state > check or we will pick it up next OOM round when we pick up the same > process (if nothing else is eligible). Or am I missing something? > That doesn't close the race, the oom killer will see the presence of an eligible TIF_MEMDIE thread in select_bad_process() and simply return to the page allocator. You'd need to thaw it there as well and hope that nothing now or in the future will get into an endless thaw-freeze-thaw loop in the exit path. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>