Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752668AbeAGJWZ convert rfc822-to-8bit (ORCPT + 1 other); Sun, 7 Jan 2018 04:22:25 -0500 Received: from mout.gmx.net ([212.227.15.19]:60958 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751396AbeAGJWX (ORCPT ); Sun, 7 Jan 2018 04:22:23 -0500 Message-ID: <1515316905.9212.5.camel@gmx.de> Subject: Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y From: Mike Galbraith To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, "Kirill A. Shutemov" , Andrew Morton , Andy Lutomirski , Borislav Petkov , Cyrill Gorcunov , Linus Torvalds , Peter Zijlstra , Thomas Gleixner , linux-mm@kvack.org, Ingo Molnar Date: Sun, 07 Jan 2018 10:21:45 +0100 In-Reply-To: <20180107091115.GB29329@kroah.com> References: <20171222084623.668990192@linuxfoundation.org> <20171222084625.007160464@linuxfoundation.org> <1515302062.6507.18.camel@gmx.de> <20180107091115.GB29329@kroah.com> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.20.5 Mime-Version: 1.0 Content-Transfer-Encoding: 8BIT X-Provags-ID: V03:K0:zUqbMtYsPLbtL+Ly4uewlmhUhT8ZzWXA1OemgG0b40Qf1kWvv9r h/RUpFcZ3NL26EihTbRuyOTnutDGb21vMkuw75ld5B6m+ZSwx7RxFW0rDjQcjUbaSL+5ULx rceTGhtTbZUIicFeUaKcpgRqBp/9hPqTM00DS7qdsrtFK07Q4WWPbkWuFAkYChzkSigRKrz jIN4AB2nHw+le2PADzifQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:ItMJKNmUiJk=:Avs9gTRiE0qtOjrEC9fHzO GHGxuaP9gkzBHwZ1+6R2+s4gznBe4DCnzMQQTQScUvZUBOkgHKSrWB5fyXpGdULc2gSg6KW3a yhLEDzuR7OZkJ51cWiuTzsybxInlfaClemBADhS4rN4rGVsRxvU+cLKKr6hRg5oWYGbNdP3WE Yq3L1mfl7SD9znxyF9mRANNW6pzHJDX/QOlL2nw6Zwdug6eo6KKaPuDnT+vNEqAKWq5zol+If lsVpOLy64dXcoQgGGEDTaU8dIMCwcsq/TYfZwN3We7PBBLHNoVWa7BBAZKCO/HLF9EjLAicnO 0ISTycsrEJnVLL/KZE+pmxXmZDeRxC6JHXJDMelJL31PbbSWOpyLORBVOxN4ydeOH8KoKB8Z6 tKbQfuKOCJme+y0HNKlpmCkgxRVIR8wKcARVDlvvZaiYAHzNFwjFp3cASLsweIYatO9Tma6X/ xUryILxGuoNaviGhsh6U2Yli7rZZ1pdSv4fFLsO95Q52u8/sas0OgRGTbnpiAhermGgHMIat1 m1ehF7O+g8Md616OCfH9QxpZmnnbkEC9NkQYNENtq3QqLSc4F6t2L4hy1Mkq+zOFF83EiR79V V3SDvCikggqQOh9NsmtAx8BqhbJhVwJfRfknK1R2BwudblxG3UbzIg3Bd5kx6xHNHxxXLmBI9 6bwu2TRjEA9jKonM2tSiySjfqW/ueO9/S+LIA/D5yWwcFK9MoAiroNMOPdHqo2JAYaCgkx93K PRPyD0eeQIDR7KSKS++6g4Qmw9Cxt3A9J2q87UT/8ATM6p98jRfNqvBZhrLj1lhFwh6tSUseo XIm2B0Wgjh4+VkrY6KTro3otK8z0WmUVovAGc6p7T95kJHd1aY= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Sun, 2018-01-07 at 10:11 +0100, Greg Kroah-Hartman wrote: > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > FYI, this broke kdump, or rather the makedumpfile part thereof. > > ?Forward looking wreckage is par for the kdump course, but... > > Is it also broken in Linus's tree with this patch? Or is there an > add-on patch that I should apply to 4.14 to resolve this issue there? Yeah, it's belly up. ?By its very nature, it's gonna get dinged up regularly. ?I only mentioned it because it's not expected that stuff gets dinged up retroactively. -Mike