From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1515207534.21799.0.camel@gmx.de> Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review From: Mike Galbraith To: Hugh Dickins Cc: Greg Kroah-Hartman , Guenter Roeck , linux-kernel , Linus Torvalds , Andrew Morton , Shuah Khan , patches@kernelci.org, Ben Hutchings , lkft-triage@lists.linaro.org, stable , Tao Wu Date: Sat, 06 Jan 2018 03:58:54 +0100 In-Reply-To: References: <20180103195056.837404126@linuxfoundation.org> <20180104234555.GA4143@roeck-us.net> <1515127074.7787.12.camel@gmx.de> <20180105121701.GD19551@kroah.com> <1515157397.7787.24.camel@gmx.de> <20180105133434.GC12036@kroah.com> <1515160990.7787.33.camel@gmx.de> Content-Type: text/plain; charset="ISO-8859-15" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On Fri, 2018-01-05 at 15:28 -0800, Hugh Dickins wrote: > On Fri, Jan 5, 2018 at 6:03 AM, Mike Galbraith wrote: > > On Fri, 2018-01-05 at 14:34 +0100, Greg Kroah-Hartman wrote: > >> > >> Ok, we found two patches that were missing in 4.4-stable that were in > >> the SLES12 tree (thanks to Jamie Iles), now I only have 19k more to sift > >> through :) > > > > As you know, in enterprise, uname -r means you might find something > > this old in your kernel if you look hard enough :) > > Mike, I think there's a good chance that Greg's 4.4.110 final will fix > your "segfault at ffffffffff5ff100" crashes: please give it a try when > you can, and let us know - thanks. Already done, and yes, it did. -Mike