From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@xensource.com>
Cc: Andrew Morton <akpm@osdl.org>,
Ian Pratt <ian.pratt@xensource.com>,
Xen-devel <xen-devel@lists.xensource.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Chris Wright <chrisw@sous-sol.org>,
Virtualization <virtualization@lists.osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux
Date: Tue, 22 Aug 2006 08:11:26 -0700 [thread overview]
Message-ID: <44EB1E9E.5030307@goop.org> (raw)
In-Reply-To: <1156256777.5091.93.camel@localhost.localdomain>
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
prev parent reply other threads:[~2006-08-22 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 14:26 [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux Ian Campbell
2006-08-22 14:48 ` Andi Kleen
2006-08-22 14:59 ` [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux II Andi Kleen
2006-08-22 15:13 ` Jeremy Fitzhardinge
2006-08-22 15:26 ` Ian Campbell
2006-08-22 15:11 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44EB1E9E.5030307@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@xensource.com \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=clameter@sgi.com \
--cc=ebiederm@xmission.com \
--cc=ian.pratt@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).