Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 6 Jul 2018 05:22:36 -0700
From:   "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To:     Michal Hocko <mhocko@kernel.org>
Cc:     Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
        David Rientjes <rientjes@google.com>, linux-mm@kvack.org,
        Andrew Morton <akpm@linux-foundation.org>,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm,oom: Bring OOM notifier callbacks to outside of OOM
 killer.
Reply-To: paulmck@linux.vnet.ibm.com
References: <20180628113942.GD32348@dhcp22.suse.cz>
 <20180628213105.GP3593@linux.vnet.ibm.com>
 <20180629090419.GD13860@dhcp22.suse.cz>
 <20180629125218.GX3593@linux.vnet.ibm.com>
 <20180629132638.GD5963@dhcp22.suse.cz>
 <20180630170522.GZ3593@linux.vnet.ibm.com>
 <20180702213714.GA7604@linux.vnet.ibm.com>
 <20180703072413.GD16767@dhcp22.suse.cz>
 <20180703160101.GC3593@linux.vnet.ibm.com>
 <20180706053942.GF32658@dhcp22.suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180706053942.GF32658@dhcp22.suse.cz>
User-Agent: Mutt/1.5.21 (2010-09-15)
Message-Id: <20180706122236.GB3593@linux.vnet.ibm.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Jul 06, 2018 at 07:39:42AM +0200, Michal Hocko wrote:
> On Tue 03-07-18 09:01:01, Paul E. McKenney wrote:
> > On Tue, Jul 03, 2018 at 09:24:13AM +0200, Michal Hocko wrote:
> > > On Mon 02-07-18 14:37:14, Paul E. McKenney wrote:
> > > [...]
> > > > commit d2b8d16b97ac2859919713b2d98b8a3ad22943a2
> > > > Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > > > Date:   Mon Jul 2 14:30:37 2018 -0700
> > > > 
> > > >     rcu: Remove OOM code
> > > >     
> > > >     There is reason to believe that RCU's OOM code isn't really helping
> > > >     that much, given that the best it can hope to do is accelerate invoking
> > > >     callbacks by a few seconds, and even then only if some CPUs have no
> > > >     non-lazy callbacks, a condition that has been observed to be rare.
> > > >     This commit therefore removes RCU's OOM code.  If this causes problems,
> > > >     it can easily be reinserted.
> > > >     
> > > >     Reported-by: Michal Hocko <mhocko@kernel.org>
> > > >     Reported-by: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
> > > >     Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > > 
> > > I would also note that waiting in the notifier might be a problem on its
> > > own because we are holding the oom_lock and the system cannot trigger
> > > the OOM killer while we are holding it and waiting for oom_callback_wq
> > > event. I am not familiar with the code to tell whether this can deadlock
> > > but from a quick glance I _suspect_ that we might depend on __rcu_reclaim
> > > and basically an arbitrary callback so no good.
> > > 
> > > Acked-by: Michal Hocko <mhocko@suse.com>
> > > 
> > > Thanks!
> > 
> > Like this?
> 
> Thanks!

Very good, queued for the merge window after next, that is, whatever
number after v4.19.  ;-)

							Thanx, Paul