Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753827AbeAGMol convert rfc822-to-8bit (ORCPT + 1 other); Sun, 7 Jan 2018 07:44:41 -0500 Received: from mout.gmx.net ([212.227.15.19]:62722 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752984AbeAGMoj (ORCPT ); Sun, 7 Jan 2018 07:44:39 -0500 Message-ID: <1515329042.13953.14.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: Michal Hocko , 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 13:44:02 +0100 In-Reply-To: <20180107101847.GC24862@dhcp22.suse.cz> References: <20171222084623.668990192@linuxfoundation.org> <20171222084625.007160464@linuxfoundation.org> <1515302062.6507.18.camel@gmx.de> <20180107091115.GB29329@kroah.com> <20180107101847.GC24862@dhcp22.suse.cz> 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:t1mPoKwZl8+nnuhH4FbmnL2t/QbR+baU+u390A4vIGf1Ozvz3xc 5JQsJ/1gaNjVMripj0DuxXpumnTId5Z+dzBrbENAg9ZX/ieJH0yk4NU7nWJGL6N+19shtwu k9ngkBKNNZ6AZxlmtk1YYFSFUUYshMGkDdqzHroDo+wpB6WAjyXlO2E8CFIjYak1DrALSii YRqGY3Az512Qz5B1gsajg== X-UI-Out-Filterresults: notjunk:1;V01:K0:4pBrQT7WxsQ=:HZJDFmEpXSgtHsesmIKavv lMQMr298gOlWKDxBJ/k16MAlKQsmKSbQTPh6HA67LWYeEfvS41ZV0cwJ60u8S6gWXf+JzOn1E wrUy0+mu2r4IbfQijbn8oj7crJnIqLgrlZtfIJZ2Su0GVSpzP7vQ2SbUn01PXIpY/HdDQyx88 oAthXHVfb6PLcc5Z4+ZLdnpMFDxObkiZaI96FOE1fhbGrf3xeDehRz4laxNYEgKHtJyGe3dN0 cMAyn+EMhazD0x7RbD+2Qv/X9j+fj7Jx3z6X7k4UMvui0f/VAAFFdpew6UhacuEXSaG9ZTHh4 Qz25Xhn68wv+UvKgrd2gBIB/vJTDRsFdTJgoUl3qdKUj3Yxc3VIQLHnw7hLS4d1DEnZp52Aq3 B4h4eMTumZwL1/x9DEHYfcXkYY3Ukbf2S1ybIRNjyaab3vEGuhaQoXr5XxwtNDWa8WnJU3+jF 7mwiH+ILn3dwpwr945mAuKHrNxgfGYib/umr5BvBT5XdWCyhkij1crY26zVSRFIzS38Go4xQU CVbgaPp8QfSxa5Nz45yHxd5jwL9gAy3UPHgvK+sMNJVgU9JIUq2xdCOE4HjAqOtW14JUooSEN +RPbFEbgZAI/B5/TUHZSX3+VNgtoHkEs1VCqaDaMPEutvz2+iLNFJkcU1KpCAis4X8SfmBmWs qoe5xV6kORsJ5iuKGfc0B5MpAOuPkzpg9qlEAytezEQ8sdyeM5GlZhR9jCzWWEb/5k4E+M+jS tpEn5hGJhH3rvmGxenbsnZZVSHnUm17BHMNOWc6VNqsawwlUhG32m/+lTRQ7Q6eme0aMqA7e6 cyDwUklnbie7mxwapq89eaTdSn75PV06tOpKqqYulEeVtjDzBs= 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 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. -Mike