[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180717112017.GA17910@kroah.com>
Date: Tue, 17 Jul 2018 13:20:17 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Nathan Chancellor <natechancellor@...il.com>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
Jiri Slaby <jslaby@...e.cz>
Subject: Re: Linux 4.17.7
On Tue, Jul 17, 2018 at 04:11:26AM -0700, Nathan Chancellor wrote:
> 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").
Ah, I missed that! Now queued up, let's run this on my build system and
then push it out for the world to test in a few hours.
thanks,
greg k-h
Powered by blists - more mailing lists