Tetsuo Handa wrote: > > > By the way, I noticed that mem_cgroup_out_of_memory() might have a bug about its > > > return value. It returns true if hit OOM_SCAN_ABORT after chosen != NULL, false > > > if hit OOM_SCAN_ABORT before chosen != NULL. Which is expected return value? > > > > true. Care to send a patch? > > I don't know what memory_max_write() wants to do when it found a TIF_MEMDIE thread > in the given memcg. Thus, I can't tell whether setting chosen to NULL (which means > mem_cgroup_out_of_memory() returns false) is the expected behavior. > Oops. "true" not "True" in this case meant "1" !? -- 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>