On Tue, Oct 24, 2017 at 06:22:13PM +0200, Michal Hocko wrote:
> On Tue 24-10-17 12:06:37, Johannes Weiner wrote:
> > > *
> > > - * That's why we don't do anything here except remember the
> > > - * OOM context and then deal with it at the end of the page
> > > - * fault when the stack is unwound, the locks are released,
> > > - * and when we know whether the fault was overall successful.
> > > + * Please note that mem_cgroup_oom_synchronize might fail to find a
> > > + * victim and then we have rely on mem_cgroup_oom_synchronize otherwise
> > > + * we would fall back to the global oom killer in pagefault_out_of_memory
> >
> > Ah, that's why... Ugh, that's really duct-tapey.
>
> As you know, I really hate the #PF OOM path. We should get rid of it.
I agree, but this isn't getting rid of it, it just adds more layers.
> > > @@ -2007,8 +2021,11 @@ static int try_charge(struct mem_cgroup *memcg, gfp_t gfp_mask,
> > >
> > > mem_cgroup_event(mem_over_limit, MEMCG_OOM);
> > >
> > > - mem_cgroup_oom(mem_over_limit, gfp_mask,
> > > - get_order(nr_pages * PAGE_SIZE));
> > > + if (mem_cgroup_oom(mem_over_limit, gfp_mask,
> > > + get_order(nr_pages * PAGE_SIZE))) {
> > > + nr_retries = MEM_CGROUP_RECLAIM_RETRIES;
> > > + goto retry;
> > > + }
> >
> > As per the previous email, this has to goto force, otherwise we return
> > -ENOMEM from syscalls once in a blue moon, which makes verification an
> > absolute nightmare. The behavior should be reliable, without weird p99
> > corner cases.
> >
> > I think what we should be doing here is: if a charge fails, set up an
> > oom context and force the charge; add mem_cgroup_oom_synchronize() to
> > the end of syscalls and kernel-context faults.
>
> What would prevent a runaway in case the only process in the memcg is
> oom unkillable then?
In such a scenario, the page fault handler would busy-loop right now.
Disabling oom kills is a privileged operation with dire consequences
if used incorrectly. You can panic the kernel with it. Why should the
cgroup OOM killer implement protective semantics around this setting?
Breaching the limit in such a setup is entirely acceptable.
Really, I think it's an enormous mistake to start modeling semantics
based on the most contrived and non-sensical edge case configurations.
Start the discussion with what is sane and what most users should
optimally experience, and keep the cornercases simple.
