On Wed, Nov 05, 2014 at 06:46:09PM +0100, Michal Hocko wrote: > Because out_of_memory can be called from mutliple paths. And > the only interesting one should be the page allocation path. > pagefault_out_of_memory is not interesting because it cannot happen for > the frozen task. Hmmm.... wouldn't that be broken by definition tho? So, if the oom killer is invoked from somewhere else than page allocation path, it would proceed ignoring the disabled setting and would race against PM freeze path all the same. Why are things broken at such basic levels? Something named oom_killer_disable does a lame attempt at it and not even that depending on who's calling. There probably is a history leading to the current situation but the level that things are broken at is too basic and baffling. :( -- tejun -- 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>