On Wed 09-03-16 08:05:11, Tetsuo Handa wrote:
[...]
> Also, what is the reason we do not need below change?
> I think there is a small race window because oom_killer_disabled needs to be
> checked after oom_killer_disable() held oom_lock. Is it because all userspace
> processes except current are frozen before oom_killer_disable() is called and
> not-yet frozen threads (i.e. kernel threads) never call mem_cgroup_out_of_memory() ?
Please refer to c32b3cbe0d06 ("oom, PM: make OOM detection in the
freezer path raceless"). It should explain this.
--
Michal Hocko
SUSE Labs
--
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>