lkml.org 
[lkml]   [2009]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH v3 5/9] x86: mark some standard sections as broken in a vDSO
Date
Some standard sections can't work in a vDSO. Although most of them
are not very likely to ever appear there, it doesn't hurt to list
them as a precaution.

Signed-off-by: Petr Tesarik <ptesarik@suse.cz>
---
arch/x86/vdso/vdso-layout.lds.S | 25 +++++++++++++++++++++++++
1 files changed, 25 insertions(+), 0 deletions(-)

diff --git a/arch/x86/vdso/vdso-layout.lds.S b/arch/x86/vdso/vdso-layout.lds.S
index 3d34d66..74fc5ae 100644
--- a/arch/x86/vdso/vdso-layout.lds.S
+++ b/arch/x86/vdso/vdso-layout.lds.S
@@ -76,6 +76,31 @@ SECTIONS
*/
.broken : {
/*
+ * Code in the Procedure Linkage Table will segfault.
+ */
+ *(.plt)
+
+ /*
+ * Nobody does the final relocation to fixup prelinked
+ * addresses for the actual vDSO base address.
+ */
+ *(.rel*)
+
+ /*
+ * Initialization/termination won't work this way.
+ */
+ *(.init) *(.fini)
+ *(.preinit_array) *(.init_array*)
+ *(.fini_array*)
+
+ /*
+ * Thread-local storage cannot be defined like this.
+ */
+ *(.tdata .tdata.* .gnu.linkonce.td.*)
+ *(.tbss .tbss.* .gnu.linkonce.tb.*)
+ *(.tcommon)
+
+ /*
* The vDSO setup code does not handle alternative
* instructions.
*/
--
1.6.0.2


\
 
 \ /
  Last update: 2009-06-16 14:59    [W:0.403 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site