On 09/20, Raymond Jennings wrote: > > On 09/20/15 11:05, Linus Torvalds wrote: >> >> which can be called from just about any context (but atomic >> allocations will never get here, so it can schedule etc). > > I think in this case the oom killer should just slap a SIGKILL on the > task and then back out, and whatever needed the memory should just wait > patiently for the sacrificial lamb to commit seppuku. Not sure I understand you correctly, but this is what we currently do. The only problem is that this doesn't work sometimes. > Also, I observed that a task in the middle of dumping core doesn't > respond to signals while it's dumping, How did you observe this? The coredumping is killable. Although yes, we have problems here in oom condition. In particular with CLONE_VM tasks. Oleg. -- 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>