From: Greg KH <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, bo.liu@linux.alibaba.com,
david@fromorbit.com, hannes@cmpxchg.org, jack@suse.cz,
kirill.shutemov@linux.intel.com, shakeelb@google.com,
stable@vger.kernel.org, torvalds@linux-foundation.org,
tytso@mit.edu, vdavydov.dev@gmail.com
Subject: Re: FAILED: patch "[PATCH] mm, memcg: fix reclaim deadlock with writeback" failed to apply to 4.4-stable tree
Date: Tue, 15 Jan 2019 16:51:31 +0100 [thread overview]
Message-ID: <20190115155131.GA17724@kroah.com> (raw)
In-Reply-To: <20190115153444.GD7283@dhcp22.suse.cz>
On Tue, Jan 15, 2019 at 04:34:44PM +0100, Michal Hocko wrote:
> I do not see a straightforward backport of this patch without pulling
> more changes in. Do we have anybody to actually hit the issue on those
> older kernels? While the issue is possible in principle I do not
> remember anybody complaining.
If no one is complaining, that's fine, you just got this message because
you put this in the commit:
> > Fixes: c3b94f44fcb0 ("memcg: further prevent OOM with too many dirty pages")
Which means any kernel newer than 4.2 (and some older stable releases)
has the issue that this patch is trying to fix. If it doesn't need to
be backported that far, wonderful!
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-15 15:51 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 [this message]
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
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=20190115155131.GA17724@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.