From: Petr Tesarik <ptesarik@suse.cz>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <andi@firstfloor.org>,
Roland McGrath <roland@redhat.com>,
Petr Tesarik <ptesarik@suse.cz>
Subject: [PATCH v3 3/9] x86: add .broken section to the vDSO linker script
Date: Tue, 16 Jun 2009 14:55:23 +0200 [thread overview]
Message-ID: <1245156929-30395-4-git-send-email-ptesarik@suse.cz> (raw)
In-Reply-To: <1245156929-30395-1-git-send-email-ptesarik@suse.cz>
This section should not contain anything unless the vDSO is
broken. It is intended to hold sections which are known not
to work correctly inside a vDSO.
If such a "broken" section is found at link-time, the linker
issues an error with a hint how to find out more.
Signed-off-by: Petr Tesarik <ptesarik@suse.cz>
---
arch/x86/vdso/vdso-layout.lds.S | 24 ++++++++++++++++++++++++
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/arch/x86/vdso/vdso-layout.lds.S b/arch/x86/vdso/vdso-layout.lds.S
index af3fa61..cc66120 100644
--- a/arch/x86/vdso/vdso-layout.lds.S
+++ b/arch/x86/vdso/vdso-layout.lds.S
@@ -73,9 +73,33 @@ SECTIONS
.text : {
*(.text*)
} :text =0x90909090
+
+ /*
+ * Some sections require some additional work from the dynamic
+ * linker to work properly. However, there is no dynamic-link
+ * pass for the vDSO, so these sections will not work.
+ * Put them into a special section and raise a link-time error
+ * if they get used by accident.
+ */
+ .broken : {
+ }
}
/*
+ * This assert is triggered if the linker finds a section in one of its
+ * input files which is known not to work inside a vDSO.
+ *
+ * To see which is the offending sections, you may:
+ * a. use objdump -h on the object files which make up the vDSO, or
+ * b. add -Wl,-M to VDSO_LDFLAGS and examine the linker map.
+ *
+ * See individual comments in the definition of the .broken section
+ * above for more information on why any given section is considered
+ * "broken".
+ */
+ASSERT(!SIZEOF(.broken), "The vdso linker script found a section that is bad. See vdso-layout.lds.S for details.");
+
+/*
* Very old versions of ld do not recognize this name token; use the constant.
*/
#define PT_GNU_EH_FRAME 0x6474e550
--
1.6.0.2
next prev parent reply other threads:[~2009-06-16 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 12:55 [PATCH v3 0/9] clean up vdso-layout.lds.S Petr Tesarik
2009-06-16 12:55 ` [PATCH v3 1/9] x86: Adjust the coding style of vdso-layout.lds.S Petr Tesarik
2009-06-16 12:55 ` [PATCH v3 2/9] x86: Remove .sdata from the vDSO linker script Petr Tesarik
2009-06-16 12:55 ` Petr Tesarik [this message]
2009-06-16 12:55 ` [PATCH v3 4/9] x86: mark altinstr-related sections in vDSO as broken Petr Tesarik
2009-06-16 12:55 ` [PATCH v3 5/9] x86: mark some standard sections as broken in a vDSO Petr Tesarik
2009-06-16 12:55 ` [PATCH v3 6/9] x86: move 32-bit vDSO padding from .data to .rodata Petr Tesarik
2009-06-16 12:55 ` [PATCH v3 7/9] x86: mark writable vDSO sections as broken Petr Tesarik
2009-06-16 12:55 ` [PATCH v3 8/9] x86: check the size of GOT in vDSO Petr Tesarik
2009-06-16 12:55 ` [PATCH v3 9/9] x86: remove .gnu.warning* sections from the vDSO Petr Tesarik
2009-06-26 11:45 ` [PATCH v3 0/9] clean up vdso-layout.lds.S Petr Tesarik
2009-06-26 17:16 ` H. Peter Anvin
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=1245156929-30395-4-git-send-email-ptesarik@suse.cz \
--to=ptesarik@suse.cz \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roland@redhat.com \
--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
all inboxes | Powered by JetHome®