All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hugh Dickins <hughd@google.com>
Cc: stable@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>,
	Sasha Levin <alexander.levin@microsoft.com>,
	Ivan Kalvachev <ikalvachev@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	Minchan Kim <minchan@kernel.org>,
	Vlastimil Babka <vbabka@suse.cz>
Subject: Re: Please add commit 145e1a71e090 to stable
Date: Sun, 3 Jun 2018 22:12:13 +0200	[thread overview]
Message-ID: <20180603201213.GA12388@kroah.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1806031201290.11416@eggly.anvils>

On Sun, Jun 03, 2018 at 01:03:48PM -0700, Hugh Dickins wrote:
> Please add 4.17 commit 145e1a71e090575c74969e3daa8136d1e5b99fc8
> ("mm: fix the NULL mapping case in __isolate_lru_page()")
> to the 4.16, 4.14, 4.9, 4.4, 3.18 and 3.2 stable kernel trees.
> 
> Two things happened after I'd sent it to Andrew without a stable tag:
> 1. Ivan posted an equivalent patch: after painstaking bisection, he
>    had found the fixed commit to be what was causing strange blocking
>    (surprising to the rest of us, we had imagined it just suboptimal).
> 2. The fixed commit arrived in five stable kernel releases (presumably
>    arriving there by auto selection: which will in due course pick up
>    this fix to it, but I don't know its cadence).

Thanks for letting us know, now queued up for 4.16, 4.14, 4.9, 4.4, and
3.18.  3.2 is now end-of-life, but 3.16 is still alive, Ben can take
care of that.

thanks,

greg k-h

      reply	other threads:[~2018-06-03 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03 20:03 Please add commit 145e1a71e090 to stable Hugh Dickins
2018-06-03 20:12 ` Greg Kroah-Hartman [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=20180603201213.GA12388@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.levin@microsoft.com \
    --cc=ben@decadent.org.uk \
    --cc=hughd@google.com \
    --cc=ikalvachev@gmail.com \
    --cc=mgorman@techsingularity.net \
    --cc=minchan@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /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.