Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751440AbdDAGtM (ORCPT ); Sat, 1 Apr 2017 02:49:12 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:40068 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751244AbdDAGtL (ORCPT ); Sat, 1 Apr 2017 02:49:11 -0400 Date: Sat, 1 Apr 2017 08:48:56 +0200 From: Greg KH To: Doug Anderson Cc: arve@android.com, riandrews@android.com, tkjos@google.com, devel@driverdev.osuosl.org, "linux-kernel@vger.kernel.org" Subject: Re: [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read() Message-ID: <20170401064856.GA14971@kroah.com> References: <20170331175341.19889-1-dianders@chromium.org> <20170331192944.GB9744@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 739 Lines: 16 On Fri, Mar 31, 2017 at 02:00:13PM -0700, Doug Anderson wrote: > On Fri, Mar 31, 2017 at 12:29 PM, Greg KH wrote: > BTW: I presume that nobody has decided that it would be a wise idea to > pick the OOM reaper code back to any stable trees? It seemed a bit > too scary to me, so I wrote a dumber (but easier to backport) solution > that avoided the deadlocks I was seeing. http://crosreview.com/465189 > and the 3 patches above it in case anyone else stumbles on this thread > and is curious. What specific upstream OOM patches are you referring to? I'm always glad to review patches for stable kernels, just email stable@vger.kernel.org the git commit ids and we can take it from there. thanks, greg k-h