Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933141AbdCVEa2 (ORCPT ); Wed, 22 Mar 2017 00:30:28 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39838 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757351AbdCVEaS (ORCPT ); Wed, 22 Mar 2017 00:30:18 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com EBB0F8553C Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dyoung@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com EBB0F8553C Date: Wed, 22 Mar 2017 12:30:04 +0800 From: Dave Young To: "Eric W. Biederman" Cc: Baoquan He , Xunlei Pang , Atsushi Kumagai , Petr Tesarik , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, kexec@lists.infradead.org, holzheu@linux.vnet.ibm.com, mahesh@linux.vnet.ibm.com, hbathini@linux.vnet.ibm.com Subject: Re: [PATCH v3 1/3] kexec: Move vmcoreinfo out of the kernel's .bss section Message-ID: <20170322043004.GB4424@dhcp-128-65.nay.redhat.com> References: <1489989033-1179-1-git-send-email-xlpang@redhat.com> <87pohbz4lo.fsf@xmission.com> <20170322025536.GA4424@dhcp-128-65.nay.redhat.com> <87pohaxam1.fsf@xmission.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87pohaxam1.fsf@xmission.com> User-Agent: Mutt/1.7.1 (2016-10-04) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Wed, 22 Mar 2017 04:30:17 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1900 Lines: 44 On 03/21/17 at 10:18pm, Eric W. Biederman wrote: > Dave Young writes: > > > On 03/20/17 at 10:33pm, Eric W. Biederman wrote: > >> Xunlei Pang writes: > >> > >> > As Eric said, > >> > "what we need to do is move the variable vmcoreinfo_note out > >> > of the kernel's .bss section. And modify the code to regenerate > >> > and keep this information in something like the control page. > >> > > >> > Definitely something like this needs a page all to itself, and ideally > >> > far away from any other kernel data structures. I clearly was not > >> > watching closely the data someone decided to keep this silly thing > >> > in the kernel's .bss section." > >> > > >> > This patch allocates extra pages for these vmcoreinfo_XXX variables, > >> > one advantage is that it enhances some safety of vmcoreinfo, because > >> > vmcoreinfo now is kept far away from other kernel data structures. > >> > >> Can you preceed this patch with a patch that removes CRASHTIME from > >> vmcoreinfo? If someone actually cares we can add a separate note that holds > >> a 64bit crashtime in the per cpu notes. > > > > I think makedumpfile is using it, but I also vote to remove the > > CRASHTIME. It is better not to do this while crashing and a makedumpfile > > userspace patch is needed to drop the use of it. > > > >> > >> As we are looking at reliability concerns removing CRASHTIME should make > >> everything in vmcoreinfo a boot time constant. Which should simplify > >> everything considerably. > > > > It is a nice improvement.. > > We also need to take a close look at what s390 is doing with vmcoreinfo. > As apparently it is reading it in a different kind of crashdump process. Yes, need careful review from s390 and maybe ppc64 especially about patch 2/3, better to have comments from IBM about s390 dump tool and ppc fadump. Added more cc. Thanks Dave