Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755943AbeAHIQL convert rfc822-to-8bit (ORCPT + 1 other); Mon, 8 Jan 2018 03:16:11 -0500 Received: from mout.gmx.net ([212.227.17.21]:60345 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755009AbeAHIQK (ORCPT ); Mon, 8 Jan 2018 03:16:10 -0500 Message-ID: <1515399333.20268.23.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 , Michal Hocko 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: Mon, 08 Jan 2018 09:15:33 +0100 In-Reply-To: <20180108075308.GC24062@kroah.com> References: <20171222084623.668990192@linuxfoundation.org> <20171222084625.007160464@linuxfoundation.org> <1515302062.6507.18.camel@gmx.de> <20180107091115.GB29329@kroah.com> <20180107101847.GC24862@dhcp22.suse.cz> <1515329042.13953.14.camel@gmx.de> <20180107132309.GD24862@dhcp22.suse.cz> <20180108075308.GC24062@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:Y3LEzmVG3UpITsP99SBco5lyTvuCy9eB9pntcrFLwZbWtpN3Oel pOyJK7LrSJfHC6r3sx29NsdZmiWH1YA/fOZ9GRo4K8o9mGpne/fbZN7gGgjGUai+/pekwVQ ysisK8XvkD9lr5PsBiUe6+Ykkt27I0P4cka+W3E5axe1iauEolnxwkBF+h2FWc+XlETLv53 xlb0miwu+LhSKXDQwVMOg== X-UI-Out-Filterresults: notjunk:1;V01:K0:awwBrCXtkVo=:nP2dSZyQlhRjonmk3y/522 Eq+t7rVzLr1J3nPSM0LXqjGFl1sA0jbd7UtcBWGUXigxVXLT7tSzHCb0MZCKEbyMZjgkAtYI+ xn0hq+2qk8scsHZJqHJRREfLKoO+fXmOAzPKWEe5ov4wesf1ZsEkGFCbAH9X7gb6uwWRFau6i Q0De9O/YYbbFzrkdTzZGrZw9nTeRcSRZyOgVHlIDaOeZD9IH3qVvn4onJ4us4h2W80Kk8bYNC z2C6U9B44iySUS3XYbiAHLGNvnwmRcBAdDSpR0Bc5PK7U1eMM72Tcl2V1eSm18Cir4j3lNcMb 1Okj78MDYgaY2Ra/BtmhTQj6GHtNWnffB0V1PwniBL7Rf8emAojz8V3okEded2iO+jRFdEncc coOgkYl4OieH9Ylmv/q1CU2WfAVtxmlYCzJWMMF+YBwkPGtQucrV6n3ITHkgmYVrt3fqnS3j6 ZVhh7w4qyYcpnZGwH02RHQKSC6H8iQEOfkAKf0+gnywxEiLcX0ByO1sTIbNeddOB2Asdb+MV1 KP9aIrpmsVBOnHR2QcEJ9mM8mgrQXkjY3mDHNlj8/heuo4SfhsTFIrdiXPkL3jB9YRYJGnGuy 1VbPmrOvpb4WU7siO5cVAUOtA/094YBLL/aoMLICzIVTpAgtIqrfRcftOkCFtuym1tqpfkpmH 8fEn9pUcjQgjuUEfxajo0M0+3iTXRGMnq2z1pstitRWLB4OhJtFdRAXcaOa0w947IecCPyvBk MGGuyCQHsjpStGZFtcciMkbK5bmXxP+4WlwUivsDaqP67AKRY2QkYuvW7EY3jLeXhHkAkN+I6 8FVY38k4prdoeNrg/NWMdSgPLsa5hHlc9qHTRTnaeWvZv0v4bk= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, 2018-01-08 at 08:53 +0100, Greg Kroah-Hartman wrote: > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > > On Sun 07-01-18 10:11:15, Greg KH 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? > > > > > > > > This one http://lkml.kernel.org/r/1513932498-20350-1-git-send-email-bhe@redhat.com > > > > I guess. > > > > > > That won't unbreak kdump, else master wouldn't be broken. ?I don't care > > > deeply, or know if anyone else does, I'm just reporting it because I > > > met it and chased it down. > > > > OK, I didn't notice that d8cfbbfa0f7 ("mm/sparse.c: wrong allocation > > for mem_section") made it in after rc6. I am still wondering why > > 83e3c48729 ("mm/sparsemem: Allocate mem_section at runtime for > > CONFIG_SPARSEMEM_EXTREME=y") made it into the stable tree in the first > > place. > > It was part of the prep for the KTPI code from what I can tell. If you > think it should be reverted, just let me know and I'll be glad to do so. No preference here. ?I have to patch master regardless if I want kdump to work while I patiently wait for userspace to get fixed up (either that or use time I don't have to go fix it up myself). -Mike