From: Michal Hocko <mhocko@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
arve@android.com, riandrews@android.com,
Todd Kjos <tkjos@google.com>,
devel@driverdev.osuosl.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read()
Date: Tue, 4 Apr 2017 09:40:29 +0200 [thread overview]
Message-ID: <20170404074028.GD15132@dhcp22.suse.cz> (raw)
In-Reply-To: <CAD=FV=XLtRRVoKoSKZEvNoCWdajUsaAYhmwdVxdB+9sCMEqngQ@mail.gmail.com>
On Mon 03-04-17 11:09:32, Doug Anderson wrote:
[...]
> Maybe +Michal Hocko would have some opinions of which OOM Reaper
> patches would be good for picking into linux stable?
I am lacking context here but please note that the OOM reaper patches
alone are not sufficient to make the OOM handling lockup free. There
were quite some changes in the core OOM killer handling to make this
possible. This has been work throughout the last year and it will be
really non-trivial to backport to stable trees.
So the primary question is what are you trying to achieve?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-04-04 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170331175341.19889-1-dianders@chromium.org>
[not found] ` <20170331192944.GB9744@kroah.com>
[not found] ` <CAD=FV=X39vVZ0v2_Z5rDrJt1JcdW+N8jRkhc0bz4yqqtox2=4Q@mail.gmail.com>
[not found] ` <20170401064856.GA14971@kroah.com>
2017-04-02 2:34 ` [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read() Doug Anderson
2017-04-03 13:25 ` Greg KH
2017-04-03 18:09 ` Doug Anderson
2017-04-04 7:40 ` Michal Hocko [this message]
2017-04-04 15:10 ` Doug Anderson
2017-04-04 15:29 ` Michal Hocko
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=20170404074028.GD15132@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).