On Thu, 18 May 2017, Michal Hocko wrote: > > Nope. The OOM in a cpuset gets the process doing the alloc killed. Or what > > that changed? !!!!! > > > > At this point you have messed up royally and nothing is going to rescue > > you anyways. OOM or not does not matter anymore. The app will fail. > > Not really. If you can trick the system to _think_ that the intersection > between mempolicy and the cpuset is empty then the OOM killer might > trigger an innocent task rather than the one which tricked it into that > situation. See above. OOM Kill in a cpuset does not kill an innocent task but a task that does an allocation in that specific context meaning a task in that cpuset that also has a memory policty. Regardless of that the point earlier was that the moving logic can avoid creating temporary situations of empty sets of nodes by analysing the memory policies etc and only performing moves when doing so is safe. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
