stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.17.7
Date: Tue, 17 Jul 2018 04:11:26 -0700	[thread overview]
Message-ID: <20180717111126.GA24208@flashbox> (raw)
In-Reply-To: <20180717105929.GA18343@kroah.com>

On Tue, Jul 17, 2018 at 12:59:29PM +0200, Greg KH wrote:
> NOTE, this kernel release is broken for i386 systems.  If you are
> running such a machine, do NOT update to this release, you will not be
> able to boot properly.
> 
> I did this release anyway with this known problem as there is a fix in
> here for x86-64 systems that was nasty to track down and was affecting
> people.  Given that the huge majority of systems are NOT i386, I felt
> this was a safe release to do at this point in time.
> 
> Once the proper fix for i386 systems has been accepted into Linus's tree
> (it has been posted already), I will pick it up and do a new 4.17.y
> release so that users of those systems can update.
> 

Just a heads up, it was picked up by Linux yesterday but it wasn't
tagged for stable: d1b47a7c9efc ("mm: don't do zero_resv_unavail if
memmap is not allocated").

  parent reply	other threads:[~2018-07-17 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 10:59 Linux 4.17.7 Greg KH
2018-07-17 10:59 ` Greg KH
2018-07-17 11:11 ` Nathan Chancellor [this message]
2018-07-17 11:20   ` 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=20180717111126.GA24208@flashbox \
    --to=natechancellor@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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).