From: tip-bot for Catalin Marinas <catalin.marinas@arm.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
catalin.marinas@arm.com, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:x86/urgent] x86: Provide _sdata in the vmlinux.lds.S file
Date: Fri, 12 Jun 2009 07:31:56 GMT [thread overview]
Message-ID: <tip-1260866a271abc84274345580f3d613d3bceff87@git.kernel.org> (raw)
In-Reply-To: <20090511122105.26556.96593.stgit@pc1117.cambridge.arm.com>
Commit-ID: 1260866a271abc84274345580f3d613d3bceff87
Gitweb: http://git.kernel.org/tip/1260866a271abc84274345580f3d613d3bceff87
Author: Catalin Marinas <catalin.marinas@arm.com>
AuthorDate: Mon, 11 May 2009 13:22:00 +0100
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Fri, 12 Jun 2009 09:21:33 +0200
x86: Provide _sdata in the vmlinux.lds.S file
_sdata is a common symbol defined by many architectures and made
available to the kernel via asm-generic/sections.h. Kmemleak uses this
symbol when scanning the data sections.
[ Impact: add new global symbol ]
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
LKML-Reference: <20090511122105.26556.96593.stgit@pc1117.cambridge.arm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/vmlinux.lds.S | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S
index 4c85b2e..367e878 100644
--- a/arch/x86/kernel/vmlinux.lds.S
+++ b/arch/x86/kernel/vmlinux.lds.S
@@ -108,6 +108,8 @@ SECTIONS
/* Data */
. = ALIGN(PAGE_SIZE);
.data : AT(ADDR(.data) - LOAD_OFFSET) {
+ /* Start of data section */
+ _sdata = .;
DATA_DATA
CONSTRUCTORS
prev parent reply other threads:[~2009-06-12 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 12:22 [PATCH] x86: Provide _sdata in the vmlinux.lds.S file Catalin Marinas
2009-05-11 12:30 ` [tip:x86/kbuild] " tip-bot for Catalin Marinas
2009-06-12 7:31 ` tip-bot for Catalin Marinas [this message]
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=tip-1260866a271abc84274345580f3d613d3bceff87@git.kernel.org \
--to=catalin.marinas@arm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@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