From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f198.google.com (mail-pf0-f198.google.com [209.85.192.198]) by kanga.kvack.org (Postfix) with ESMTP id ED33F6B0302 for ; Wed, 7 Feb 2018 07:01:37 -0500 (EST) Received: by mail-pf0-f198.google.com with SMTP id u19so320312pfl.3 for ; Wed, 07 Feb 2018 04:01:37 -0800 (PST) Received: from heian.cn.fujitsu.com (mail.cn.fujitsu.com. [183.91.158.132]) by mx.google.com with ESMTP id c10si860699pge.396.2018.02.07.04.01.36 for ; Wed, 07 Feb 2018 04:01:36 -0800 (PST) Subject: Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y References: <20171222084623.668990192@linuxfoundation.org> <20171222084625.007160464@linuxfoundation.org> <1515302062.6507.18.camel@gmx.de> <20180108160444.2ol4fvgqbxnjmlpg@gmail.com> <20180108174653.7muglyihpngxp5tl@black.fi.intel.com> <20180109001303.dy73bpixsaegn4ol@node.shutemov.name> <1515469448.6766.12.camel@gmx.de> <20180207104111.sljc62bgkggmtio4@node.shutemov.name> <1518000336.29698.1.camel@gmx.de> From: Dou Liyang Message-ID: Date: Wed, 7 Feb 2018 20:00:30 +0800 MIME-Version: 1.0 In-Reply-To: <1518000336.29698.1.camel@gmx.de> Content-Type: text/plain; charset="iso-8859-15"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Mike Galbraith , "Kirill A. Shutemov" Cc: Ingo Molnar , Andrew Morton , Baoquan He , Peter Zijlstra , Greg Kroah-Hartman , Dave Young , kexec@lists.infradead.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Andy Lutomirski , linux-mm@kvack.org, Vivek Goyal , Cyrill Gorcunov , Thomas Gleixner , Borislav Petkov , Linus Torvalds , "Kirill A. Shutemov" , Takao Indoh Hi Kirill,Mike At 02/07/2018 06:45 PM, Mike Galbraith wrote: > On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: >> On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: >>> Hi All, >>> >>> I met the makedumpfile failed in the upstream kernel which contained >>> this patch. Did I missed something else? >> >> None I'm aware of. >> >> Is there a reason to suspect that the issue is related to the bug this patch >> fixed? > I did a contrastive test by my colleagues Indoh's suggestion. Revert your two commits: commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 Author: Kirill A. Shutemov Date: Fri Sep 29 17:08:16 2017 +0300 commit 629a359bdb0e0652a8227b4ff3125431995fec6e Author: Kirill A. Shutemov Date: Tue Nov 7 11:33:37 2017 +0300 ...and keep others unchanged, the makedumpfile works well. > Still works fine for me with .today. Box is only 16GB desktop box though. > Btw, In the upstream kernel which contained this patch, I did two tests: 1) use the makedumpfile as core_collector in /etc/kdump.conf, then trigger the process of kdump by echo 1 >/proc/sysrq-trigger, the makedumpfile works well and I can get the vmcore file. ......It is OK 2) use cp as core_collector, do the same operation to get the vmcore file. then use makedumpfile to do like above: [douly@localhost code]$ ./makedumpfile -d 31 --message-level 31 -x vmlinux_4.15+ vmcore_4.15+_from_cp_command vmcore_4.15+ ......It causes makedumpfile failed. Thanks, dou. > -Mike > > > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org