From: Greg KH <gregkh@linuxfoundation.org>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Michal Hocko <mhocko@kernel.org>,
akpm@linux-foundation.org, bo.liu@linux.alibaba.com,
david@fromorbit.com, hannes@cmpxchg.org, jack@suse.cz,
shakeelb@google.com, stable@vger.kernel.org,
torvalds@linux-foundation.org, tytso@mit.edu,
vdavydov.dev@gmail.com
Subject: Re: [PATCH 4.9] mm, memcg: fix reclaim deadlock with writeback
Date: Mon, 21 Jan 2019 13:21:08 +0100 [thread overview]
Message-ID: <20190121122108.GB15873@kroah.com> (raw)
In-Reply-To: <20190116114107.glr72vtt4i5kikq3@black.fi.intel.com>
On Wed, Jan 16, 2019 at 02:41:07PM +0300, Kirill A. Shutemov wrote:
> On Wed, Jan 16, 2019 at 10:48:54AM +0000, Michal Hocko wrote:
> > On Tue 15-01-19 20:57:31, Michal Hocko wrote:
> > > On Tue 15-01-19 19:09:18, Greg KH wrote:
> > [...]
> > > > Not a problem, thanks for looking into it. As you say 4.8+, this didn't
> > > > apply to 4.9 either, so do I need to look into doing a manual backport
> > > > there?
> > >
> > > Backporting there should be much more easier because we already have
> > > prealloc stuff since 4.8. I will try to find some time to look into this
> > > tomorrow but I am leaving for few days off so I cannot promise anything.
> >
> > So here we go. But this really needs another pair of eyes before
> > merging. Kirill, could you have a look please?
>
> Looks right to me.
Thanks for the review and the patch, now queued up!
greg k-h
prev parent reply other threads:[~2019-01-21 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 14:57 FAILED: patch "[PATCH] mm, memcg: fix reclaim deadlock with writeback" failed to apply to 4.4-stable tree gregkh
2019-01-15 15:34 ` Michal Hocko
2019-01-15 15:51 ` Greg KH
2019-01-15 17:40 ` Michal Hocko
2019-01-15 18:09 ` Greg KH
2019-01-15 19:57 ` Michal Hocko
2019-01-16 10:48 ` [PATCH 4.9] mm, memcg: fix reclaim deadlock with writeback Michal Hocko
2019-01-16 11:41 ` Kirill A. Shutemov
2019-01-21 12:21 ` Greg KH [this message]
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=20190121122108.GB15873@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bo.liu@linux.alibaba.com \
--cc=david@fromorbit.com \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=mhocko@kernel.org \
--cc=shakeelb@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vdavydov.dev@gmail.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).