From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:59242 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730180AbeGQLw2 (ORCPT ); Tue, 17 Jul 2018 07:52:28 -0400 Date: Tue, 17 Jul 2018 13:20:17 +0200 From: Greg KH To: Nathan Chancellor Cc: linux-kernel@vger.kernel.org, Andrew Morton , torvalds@linux-foundation.org, stable@vger.kernel.org, lwn@lwn.net, Jiri Slaby Subject: Re: Linux 4.17.7 Message-ID: <20180717112017.GA17910@kroah.com> References: <20180717105929.GA18343@kroah.com> <20180717111126.GA24208@flashbox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180717111126.GA24208@flashbox> Sender: stable-owner@vger.kernel.org List-ID: 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