From: Vivek Goyal <vgoyal@in.ibm.com>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Fastboot mailing list <fastboot@lists.osdl.org>,
Morton Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Sam Ravnborg <sam@ravnborg.org>
Subject: [PATCH 4/4] i386: Specify section flags while creating new sections
Date: Wed, 3 Jan 2007 17:04:55 +0530 [thread overview]
Message-ID: <20070103113455.GI17546@in.ibm.com> (raw)
o Older binutils (older than 2.6.15) require explicit flags to be set
for section. (if a section has been defined using "section" directive).
Otherwise a section which should have been allocatable and executable
(AX) will not have properties as per intention.
o I had put a patch in -mm which will break the things if used with
older binutils. Hence this is the fix on top of that patch.
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc2/2.6.20-rc2-mm1/broken-out/i386-move-startup_32-in-texthead-section.patch
Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
---
arch/i386/kernel/head.S | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -puN arch/i386/kernel/head.S~i386-modify-section-directive-for-older-binutils arch/i386/kernel/head.S
--- linux-2.6.20-rc2-mm1-reloc/arch/i386/kernel/head.S~i386-modify-section-directive-for-older-binutils 2007-01-03 11:58:51.000000000 +0530
+++ linux-2.6.20-rc2-mm1-reloc-root/arch/i386/kernel/head.S 2007-01-03 12:00:03.000000000 +0530
@@ -53,7 +53,7 @@
* any particular GDT layout, because we load our own as soon as we
* can.
*/
-.section .text.head
+.section .text.head,"ax",@progbits
ENTRY(startup_32)
#ifdef CONFIG_PARAVIRT
@@ -155,9 +155,9 @@ page_pde_offset = (__PAGE_OFFSET >> 20);
*/
#ifdef CONFIG_HOTPLUG_CPU
-.section .text
+.section .text,"ax",@progbits
#else
-.section .init.text
+.section .init.text,"ax",@progbits
#endif
#ifdef CONFIG_SMP
_
reply other threads:[~2007-01-03 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070103113455.GI17546@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.