From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932301AbWHVPL3 (ORCPT ); Tue, 22 Aug 2006 11:11:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932307AbWHVPL3 (ORCPT ); Tue, 22 Aug 2006 11:11:29 -0400 Received: from gw.goop.org ([64.81.55.164]:33463 "EHLO mail.goop.org") by vger.kernel.org with ESMTP id S932301AbWHVPL2 (ORCPT ); Tue, 22 Aug 2006 11:11:28 -0400 Message-ID: <44EB1E9E.5030307@goop.org> Date: Tue, 22 Aug 2006 08:11:26 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 1.5.0.4 (X11/20060613) MIME-Version: 1.0 To: Ian Campbell CC: Andi Kleen , Andrew Morton , Ian Pratt , Xen-devel , Chris Wright , Virtualization , Christoph Lameter , Linux Kernel , "Eric W. Biederman" Subject: Re: [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux References: <1156256777.5091.93.camel@localhost.localdomain> In-Reply-To: <1156256777.5091.93.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ian Campbell wrote: > It has been suggested to me that the notes segment should have flags 0 > (i.e. not readable) since it is only used by the loader and is not used > at runtime. For now I went with a readable segment since that is what > the i386 patch uses. > Note that the PT_NOTEs segment is aliased to a part of one of the PT_LOADs - ie, it points into the data segment. So making it -rwx would either be ignored, or also require putting the bits into a new PT_LOAD segment with 0 permissions, which is pretty pointless. I made it R_E just so there was no permissions conflict, though the _E part could probably go. J