From: "Jan Beulich" <JBeulich@novell.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: mingo@elte.hu, tglx@linutronix.de, linux-arch@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
hpa@zytor.com
Subject: Re: [PATCH] allow placing exception table in .rodata (and do so on x86)
Date: Thu, 28 Apr 2011 12:40:58 +0100 [thread overview]
Message-ID: <4DB96E6A020000780003E9EB@vpn.id2.novell.com> (raw)
In-Reply-To: <20110428104306.GC2431@osiris.boeblingen.de.ibm.com>
>>> On 28.04.11 at 12:43, Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> On Wed, Apr 27, 2011 at 04:36:04PM +0100, Jan Beulich wrote:
>> This is since the table is really a set of pointers, i.e. misplaced in
>> .text.
>>
>> Quite likely other architectures would want to follow.
>>
>> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>>
>
> [...]
>
>> --- 2.6.39-rc5/include/asm-generic/vmlinux.lds.h
>> +++ 2.6.39-rc5-extable-in-rodata/include/asm-generic/vmlinux.lds.h
>> @@ -226,6 +226,7 @@
>> *(.rodata1) \
>> } \
>> \
>> + EXCEPTION_TABLE_RO \
>
> That's odd. The kernel actually writes to it (sort_main_extable()), so
> it shouldn't be in the ro data section, but the data section.
This area does get written, but only at boot time, before read-only
data gets set to r/o (on x86 at least). With this in mind, it's better
to place it in .rodata, as that way run-time protection will be in place
(and I think you agree that it was misplaced in .text in any case).
Jan
>> JUMP_TABLE \
>
> same here.
next prev parent reply other threads:[~2011-04-28 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 15:36 [PATCH] allow placing exception table in .rodata (and do so on x86) Jan Beulich
2011-04-28 10:43 ` Heiko Carstens
2011-04-28 11:40 ` Jan Beulich [this message]
2011-04-28 11:40 ` Jan Beulich
2011-04-28 11:47 ` Geert Uytterhoeven
2011-04-28 12:07 ` Jan Beulich
2011-04-28 12:53 ` Heiko Carstens
2011-04-28 12:53 ` Heiko Carstens
2011-04-28 13:31 ` Jan Beulich
2011-04-28 13:31 ` Jan Beulich
2011-04-28 13:44 ` Geert Uytterhoeven
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=4DB96E6A020000780003E9EB@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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).