On Thu 11-11-21 15:42:01, Mina Almasry wrote: > On remote ooms (OOMs due to remote charging), the oom-killer will attempt > to find a task to kill in the memcg under oom, if the oom-killer > is unable to find one, the oom-killer should simply return ENOMEM to the > allocating process. This really begs for some justification. > If we're in pagefault path and we're unable to return ENOMEM to the > allocating process, we instead kill the allocating process. Why do you handle those differently? > Signed-off-by: Mina Almasry <almasrymina@xxxxxxxxxx> > > Cc: Michal Hocko <mhocko@xxxxxxxx> > Cc: Theodore Ts'o <tytso@xxxxxxx> > Cc: Greg Thelen <gthelen@xxxxxxxxxx> > Cc: Shakeel Butt <shakeelb@xxxxxxxxxx> > Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Cc: Hugh Dickins <hughd@xxxxxxxxxx> > CC: Roman Gushchin <guro@xxxxxx> > Cc: Johannes Weiner <hannes@xxxxxxxxxxx> > Cc: Hugh Dickins <hughd@xxxxxxxxxx> > Cc: Tejun Heo <tj@xxxxxxxxxx> > Cc: Vladimir Davydov <vdavydov.dev@xxxxxxxxx> > Cc: Muchun Song <songmuchun@xxxxxxxxxxxxx> > Cc: riel@xxxxxxxxxxx > Cc: linux-mm@xxxxxxxxx > Cc: linux-fsdevel@xxxxxxxxxxxxxxx > Cc: cgroups@xxxxxxxxxxxxxxx -- Michal Hocko SUSE Labs
