mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Doug Anderson <dianders@chromium.org>
Cc: arve@android.com, riandrews@android.com, tkjos@google.com,
	devel@driverdev.osuosl.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read()
Date: Sat, 1 Apr 2017 08:48:56 +0200	[thread overview]
Message-ID: <20170401064856.GA14971@kroah.com> (raw)
In-Reply-To: <CAD=FV=X39vVZ0v2_Z5rDrJt1JcdW+N8jRkhc0bz4yqqtox2=4Q@mail.gmail.com>

On Fri, Mar 31, 2017 at 02:00:13PM -0700, Doug Anderson wrote:
> On Fri, Mar 31, 2017 at 12:29 PM, Greg KH <gregkh@linuxfoundation.org> 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

  reply	other threads:[~2017-04-01  6:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 17:53 Douglas Anderson
2017-03-31 19:29 ` Greg KH
2017-03-31 21:00   ` Doug Anderson
2017-04-01  6:48     ` Greg KH [this message]
2017-04-02  2:34       ` Doug Anderson
2017-04-03 13:25         ` Greg KH
2017-04-03 18:09           ` Doug Anderson
2017-04-04  7:40             ` Michal Hocko
2017-04-04 15:10               ` Doug Anderson
2017-04-04 15:29                 ` Michal Hocko
2017-04-03 13:47 ` peter enderborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170401064856.GA14971@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dianders@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riandrews@android.com \
    --cc=tkjos@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome