Michal Hocko writes:
How does this play wit the actual OOM when the user expects oom to resolve the situation because the reclaim is futile and there is nothing reclaimable except for killing a process?
In addition to what Johannes said, this doesn't impede OOM in the case of global system starvation (eg. in the case that all major consumers of memory are allocator throttling). In that case nothing unusual will happen, since the task's state is TASK_KILLABLE rather than TASK_UNINTERRUPTIBLE, and we will exit out of mem_cgroup_handle_over_high as quickly as possible.
