x86: move both exception tables into .rodata

While they are being written during early boot (when sorting them),
that writing takes place before we actually start fiddling with page
table permissions, so these tables can benefit from getting write
protected just like ordinary r/o data does (for now only when using
2M mappings).

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
This commit is contained in:
Jan Beulich committed 2016-03-15 12:21:38 +01:00
1 parent 0b8a172444
commit 79713ed0a9
1 file changed
+11 -10
+11 -10
View File
@@ -76,6 +76,17 @@ SECTIONS
*(.rodata)
*(.rodata.*)
. = ALIGN(8);
/* Exception table */
__start___ex_table = .;
*(.ex_table)
__stop___ex_table = .;
/* Pre-exception table */
__start___pre_ex_table = .;
*(.ex_table.pre)
__stop___pre_ex_table = .;
#ifdef LOCK_PROFILE
. = ALIGN(POINTER_ALIGN);
__lock_profile_start = .;
@@ -162,16 +173,6 @@ SECTIONS
__2M_rwdata_start = .; /* Start of 2M superpages, mapped RW. */
. = ALIGN(SMP_CACHE_BYTES);
.data.read_mostly : {
/* Exception table */
__start___ex_table = .;
*(.ex_table)
__stop___ex_table = .;
/* Pre-exception table */
__start___pre_ex_table = .;
*(.ex_table.pre)
__stop___pre_ex_table = .;
*(.data.read_mostly)
. = ALIGN(8);
__start_schedulers_array = .;
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.