Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933412Ab3CUOMW (ORCPT ); Thu, 21 Mar 2013 10:12:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57486 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757636Ab3CUOMV (ORCPT ); Thu, 21 Mar 2013 10:12:21 -0400 Date: Thu, 21 Mar 2013 10:12:02 -0400 From: Vivek Goyal To: HATAYAMA Daisuke Cc: ebiederm@xmission.com, cpw@sgi.com, kumagai-atsushi@mxc.nes.nec.co.jp, lisa.mitchell@hp.com, heiko.carstens@de.ibm.com, akpm@linux-foundation.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, zhangyanfei@cn.fujitsu.com Subject: Re: [PATCH v3 01/21] vmcore: reference e_phoff member explicitly to get position of program header table Message-ID: <20130321141202.GF3934@redhat.com> References: <20130316040003.15064.62308.stgit@localhost6.localdomain6> <20130316040053.15064.93652.stgit@localhost6.localdomain6> <87ppyvnjyn.fsf@xmission.com> <20130321.115041.225288996.d.hatayama@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130321.115041.225288996.d.hatayama@jp.fujitsu.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2098 Lines: 46 On Thu, Mar 21, 2013 at 11:50:41AM +0900, HATAYAMA Daisuke wrote: > From: "Eric W. Biederman" > Subject: Re: [PATCH v3 01/21] vmcore: reference e_phoff member explicitly to get position of program header table > Date: Tue, 19 Mar 2013 14:44:16 -0700 > > > HATAYAMA Daisuke writes: > > > >> Currently, the code assumes that position of program header table is > >> next to ELF header. But future change can break the assumption on > >> kexec-tools and the 1st kernel. To avoid worst case, reference e_phoff > >> member explicitly to get position of program header table in > >> file-offset. > > > > In principle this looks good. However when I read this it looks like > > you are going a little too far. > > > > You are changing not only the reading of the supplied headers, but > > you are changing the generation of the new new headers that describe > > the data provided by /proc/vmcore. > > > > I get lost in following this after you mangle merge_note_headers. > > > > In principle removing silly assumptions seems reasonable, but I think > > it is completely orthogonal to the task of maping vmcore mmapable. > > > > I think it is fine to claim that the assumptions made here in vmcore are > > part of the kexec on panic ABI at this point, which would generally make > > this change unnecessary. > > This was suggested by Vivek. He prefers generic one. > > Vivek, do you agree to this? Or is it better to re-post this and other > clean-up patches as another one separately to this patch set? Given the fact that current code has been working, I am fine to just re-post and take care of mmap() related issues. And we can take care of cleaning up of some assumptions about PT_NOTE headers later. Trying to club large cleanup with mmap() patches is making it hard to review. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/