From: Ian Campbell <Ian.Campbell@XenSource.com>
To: vgoyal@in.ibm.com
Cc: Jan Beulich <jbeulich@novell.com>, Andi Kleen <ak@suse.de>,
Magnus Damm <magnus@valinux.co.jp>,
linux-kernel@vger.kernel.org, patches@x86-64.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [patches] [PATCH] [18/19] x86_64: Overlapping program headers in physical addr space fix
Date: Mon, 23 Oct 2006 16:02:44 +0100 [thread overview]
Message-ID: <1161615765.22514.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20061023144145.GB15532@in.ibm.com>
On Mon, 2006-10-23 at 10:41 -0400, Vivek Goyal wrote:
> On Mon, Oct 23, 2006 at 08:20:38AM +0100, Jan Beulich wrote:
> > >@@ -17,6 +17,7 @@ PHDRS {
> > > text PT_LOAD FLAGS(5); /* R_E */
> > > data PT_LOAD FLAGS(7); /* RWE */
> > > user PT_LOAD FLAGS(7); /* RWE */
> > >+ data.init PT_LOAD FLAGS(7); /* RWE */
> > > note PT_NOTE FLAGS(4); /* R__ */
> > > }
> > > SECTIONS
> >
> > Even though it's only cosmetic, I think it would have been
> > more than appropriate to remove the ill 'E' permission on data
> > with that change.
>
> May be. I just kept it because already data segment had 'E' permissions.
> Ian, any reason why did you keep 'E' on data segment? If it is not
> intentional, I will get rid of it.
I wasn't 100% sure (only 99% :-)) it was unneeded so I kept it to
minimise the changes in the final image since the original .data section
had it.
> >(Btw., why does 'note' need 'R'?)
>
> I went through the comments Ian had put in his patch. There also he
> mentions that people objected to 'R' permissions for note segment as
> it is read only by boot loader. He kept it because i386 had the similar
> thing.
>
> Ian, again if there is no specific reason to keep 'R' for note, I will
> get rid of it.
There was a suggestion at one point that the note section was aliased by
a PT_LOAD and so needed the R but it turned out that wasn't the case.
You can drop it as far as I'm concerned.
Ian.
next prev parent reply other threads:[~2006-10-23 15:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061021 651.356252000@suse.de>
2006-10-21 16:51 ` [PATCH] [1/19] x86_64: Update defconfig Andi Kleen
2006-10-21 16:51 ` [PATCH] [2/19] i386: " Andi Kleen
2006-10-21 16:51 ` [PATCH] [3/19] x86_64: x86_64 hot-add memory srat.c fix Andi Kleen
2006-10-21 16:51 ` [PATCH] [4/19] x86_64: typo in __assign_irq_vector when updating pos for vector and offset Andi Kleen
2006-10-21 16:51 ` [PATCH] [5/19] i386: fix .cfi_signal_frame copy-n-paste error Andi Kleen
2006-10-21 16:51 ` [PATCH] [6/19] x86_64: Fix for arch/x86_64/pci/Makefile CFLAGS Andi Kleen
2006-10-21 16:51 ` [PATCH] [7/19] x86_64: fix page align in e820 allocator Andi Kleen
2006-10-21 16:51 ` [PATCH] [8/19] x86: Use -maccumulate-outgoing-args Andi Kleen
2006-10-21 17:18 ` Dave Jones
2006-10-21 18:20 ` Andi Kleen
2006-10-21 16:51 ` [PATCH] [9/19] x86_64: Speed up dwarf2 unwinder Andi Kleen
2006-10-21 16:51 ` [PATCH] [10/19] x86_64: x86_64 add NX mask for PTE entry Andi Kleen
2006-10-21 16:51 ` [PATCH] [11/19] i386: Fix fake return address Andi Kleen
2006-10-21 18:12 ` Jeremy Fitzhardinge
2006-10-21 18:14 ` Andi Kleen
2006-10-21 18:17 ` Andreas Schwab
2006-10-21 16:51 ` [PATCH] [12/19] x86_64: Fix ENOSYS in system call tracing Andi Kleen
2006-10-21 16:51 ` [PATCH] [13/19] x86_64: Revert interrupt backlink changes Andi Kleen
2006-10-21 16:51 ` [PATCH] [14/19] i386: Disable nmi watchdog on all ThinkPads Andi Kleen
2006-10-21 17:24 ` Dave Jones
2006-10-21 18:11 ` [patches] " Andi Kleen
2006-10-21 18:14 ` Dave Jones
2006-10-21 18:22 ` Andi Kleen
2006-10-21 16:51 ` [PATCH] [16/19] x86: Revert new unwind kernel stack termination Andi Kleen
2006-10-21 16:51 ` [PATCH] [18/19] x86_64: Overlapping program headers in physical addr space fix Andi Kleen
2006-10-23 7:20 ` [patches] " Jan Beulich
2006-10-23 14:41 ` Vivek Goyal
2006-10-23 15:02 ` Ian Campbell [this message]
2006-10-23 16:08 ` Jan Beulich
2006-10-21 16:51 ` [PATCH] [19/19] x86_64: Revert timer routing behaviour back to 2.6.16 state Andi Kleen
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=1161615765.22514.13.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus@valinux.co.jp \
--cc=patches@x86-64.org \
--cc=vgoyal@in.ibm.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