From: Greg KH <gregkh@linuxfoundation.org>
To: Mel Gorman <mgorman@suse.de>
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mm, mprotect: flush TLB if potentially racing with a parallel" failed to apply to 4.4-stable tree
Date: Tue, 8 Aug 2017 09:14:09 -0700 [thread overview]
Message-ID: <20170808161409.GC20707@kroah.com> (raw)
In-Reply-To: <20170808084235.t3rntgpmx7jjbqd7@suse.de>
On Tue, Aug 08, 2017 at 09:42:36AM +0100, Mel Gorman wrote:
> On Mon, Aug 07, 2017 at 12:54:30PM -0700, Greg Kroah-Hartman wrote:
> >
> > The patch below does not apply to the 4.4-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > ------------------ original commit in Linus's tree ------------------
> >
> > From 3ea277194daaeaa84ce75180ec7c7a2075027a68 Mon Sep 17 00:00:00 2001
> > From: Mel Gorman <mgorman@suse.de>
> > Date: Wed, 2 Aug 2017 13:31:52 -0700
> > Subject: [PATCH] mm, mprotect: flush TLB if potentially racing with a parallel
> > reclaim leaving stale TLB entries
> >
>
> The backport is below. Pleas take note of "stable note for 4.4" which
> explains why it was not a clean backport and remove the note if desired.
The note was great, thanks for the backport, now queued up.
greg k-h
prev parent reply other threads:[~2017-08-08 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 19:54 FAILED: patch "[PATCH] mm, mprotect: flush TLB if potentially racing with a parallel" failed to apply to 4.4-stable tree gregkh
2017-08-08 8:42 ` Mel Gorman
2017-08-08 16:14 ` 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=20170808161409.GC20707@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mgorman@suse.de \
--cc=stable@vger.kernel.org \
/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.