From: tip-bot for Hannes Reinecke <hare@suse.de>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
sam@ravnborg.org, akpm@linux-foundation.org, hare@suse.de,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:x86/urgent] x86: Add back _end symbol that is missing from Symbol.map
Date: Sun, 8 Nov 2009 11:07:12 GMT [thread overview]
Message-ID: <tip-d1e4d37b79e944f6351ae38eb1ca7c9f7b506e76@git.kernel.org> (raw)
In-Reply-To: <200911041519.nA4FJWEW030164@imap1.linux-foundation.org>
Commit-ID: d1e4d37b79e944f6351ae38eb1ca7c9f7b506e76
Gitweb: http://git.kernel.org/tip/d1e4d37b79e944f6351ae38eb1ca7c9f7b506e76
Author: Hannes Reinecke <hare@suse.de>
AuthorDate: Wed, 4 Nov 2009 07:19:32 -0800
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sun, 8 Nov 2009 12:05:03 +0100
x86: Add back _end symbol that is missing from Symbol.map
With 2.6.31 'crash' on x86_64 falls flat on its face as the
'_end' symbol is missing from the System.map file.
The culprit is commit 091e52c3551d3031343df24b573b770b4c6c72b6,
which moved the '_end' symbol into it's own section. Apparently
this causes kallsyms to not reference it properly.
So do not include _end in it's own section.
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: <stable@kernel.org> # .31.x
LKML-Reference: <200911041519.nA4FJWEW030164@imap1.linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/vmlinux.lds.S | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S
index 3c68fe2..b2f811d 100644
--- a/arch/x86/kernel/vmlinux.lds.S
+++ b/arch/x86/kernel/vmlinux.lds.S
@@ -291,9 +291,7 @@ SECTIONS
__brk_limit = .;
}
- .end : AT(ADDR(.end) - LOAD_OFFSET) {
- _end = .;
- }
+ _end = .;
STABS_DEBUG
DWARF_DEBUG
next parent reply other threads:[~2009-11-08 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200911041519.nA4FJWEW030164@imap1.linux-foundation.org>
2009-11-08 11:07 ` tip-bot for Hannes Reinecke [this message]
2009-11-08 11:38 ` Sam Ravnborg
2009-11-08 11:48 ` Ingo Molnar
2009-11-08 12:38 ` Sam Ravnborg
2009-11-08 12:42 ` Ingo Molnar
2009-11-09 18:40 ` H. Peter Anvin
2009-12-14 22:27 ` [tip:x86/urgent] x86: Regex support and known-movable symbols for relocs, fix _end tip-bot for H. Peter Anvin
2009-11-08 16:36 ` [tip:x86/urgent] x86: Add back _end symbol that is missing from Symbol.map 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=tip-d1e4d37b79e944f6351ae38eb1ca7c9f7b506e76@git.kernel.org \
--to=hare@suse.de \
--cc=akpm@linux-foundation.org \
--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=sam@ravnborg.org \
--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
Powered by JetHome