From: Keith Owens <kaos@ocs.com.au>
To: trivial@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org
Subject: [patch] 2.5.43 export _end
Date: Thu, 17 Oct 2002 13:12:37 +1000 [thread overview]
Message-ID: <8402.1034824357@kao2.melbourne.sgi.com> (raw)
Some programs such as ps, lkcd and others need to validate that
System.map matches the kernel. Comparing all symbol names from ksyms
against map breaks badly when faced with function descriptors (ia64 has
hundreds of mismatches because of function descriptors). lkcd attempts
to solve this problem by adding kernel_magic which contains the value
of _end, but that requires /dev/kmem access to read kernel_magic.
Trivial fix - export _end. Every arch *lds* file defines _end.
No special access is required to match ksyms _end against System.map
_end.
Index: 43.1/kernel/ksyms.c
--- 43.1/kernel/ksyms.c Wed, 16 Oct 2002 14:25:21 +1000 kaos (linux-2.5/w/d/18_ksyms.c 1.22.1.31 444)
+++ 43.1(w)/kernel/ksyms.c Thu, 17 Oct 2002 12:16:14 +1000 kaos (linux-2.5/w/d/18_ksyms.c 1.22.1.31 444)
@@ -602,3 +602,7 @@ EXPORT_SYMBOL(__per_cpu_offset);
/* debug */
EXPORT_SYMBOL(dump_stack);
+
+/* To match ksyms with System.map */
+extern const char _end[];
+EXPORT_SYMBOL(_end);
reply other threads:[~2002-10-17 3:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8402.1034824357@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).