Date:   Tue, 15 Jan 2019 16:51:31 +0100
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
Message-ID: <20190115155131.GA17724@kroah.com>
References: <154747783690179@kroah.com>
 <20190115153444.GD7283@dhcp22.suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190115153444.GD7283@dhcp22.suse.cz>
User-Agent: Mutt/1.11.2 (2019-01-07)
Sender: stable-owner@vger.kernel.org
Precedence: bulk

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