From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Cc: rusty@rustcorp.com.au, zwane@linuxpower.ca, sam@ravnborg.org
Subject: Re: [PATCH*] show last kernel-image symbol in /proc/kallsyms
Date: Mon, 10 May 2004 16:24:13 -0700 [thread overview]
Message-ID: <20040510162413.6db2d60e.rddunlap@osdl.org> (raw)
In-Reply-To: <20040510105606.27554ad0.rddunlap@osdl.org>
On Mon, 10 May 2004 10:56:06 -0700 Randy.Dunlap wrote:
| On Mon, 10 May 2004 14:14:10 +1000 Rusty Russell wrote:
|
| | On Mon, 2004-05-10 at 10:14, Randy.Dunlap wrote:
| | > 'cat' or 'tail' of /proc/kallsyms (2.6.6-rc2 or -rc3, & probably much
| | > earlier) does not include the last kernel-image symbol (_einittext).
| | >
| | > _einittext is the last symbol generated in .tmp_kallsyms2.S
| | > and the symbol count in that file also appears to be correct,
| | > but the iterator code for /proc/kallsyms comes up 1 short somehow.
| | >
| | > Here are 2 patches. Either one of them "fixes" the problem.
| | > Neither of them is the correct fix AFAIK.
| |
| | Ah, I see you are a student of the Morton school of patch extraction.
| | Well, it worked.
|
| Well.... yes.
|
| And thanks for taking time to fix it.
| It now works as expected. :)
Welllll, almost as expected. I now see _einittext as hoped and
expected. However, sometimes I don't see _etext... if it has the
same address as another (previous) symbol, which it can.
so I think that you may want this kind of patch, especially for
CONFIG_KALLSYMS_ALL.
Please apply/merge.
--
~Randy
// linux-266
// Always include the _etext symbol in /proc/kallsyms.
diffstat:=
scripts/kallsyms.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff -Naurp ./scripts/kallsyms.c~force_etext ./scripts/kallsyms.c
--- ./scripts/kallsyms.c~force_etext 2004-05-09 19:33:21.000000000 -0700
+++ ./scripts/kallsyms.c 2004-05-10 16:01:02.000000000 -0700
@@ -115,7 +115,10 @@ write_src(void)
if (!symbol_valid(&table[i]))
continue;
- if (table[i].addr == last_addr)
+ if (table[i].addr == last_addr &&
+ last_addr != _etext)
+ /* don't duplicate addresses, except always
+ * make sure that _etext is in kallsyms */
continue;
printf("\tPTR\t%#llx\n", table[i].addr);
@@ -140,7 +143,8 @@ write_src(void)
if (!symbol_valid(&table[i]))
continue;
- if (table[i].addr == last_addr)
+ if (table[i].addr == last_addr &&
+ last_addr != _etext)
continue;
for (k = 0; table[i].sym[k] && table[i].sym[k] == prev[k]; ++k)
next prev parent reply other threads:[~2004-05-10 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 0:14 Randy.Dunlap
2004-05-10 4:14 ` Rusty Russell
2004-05-10 17:56 ` Randy.Dunlap
2004-05-10 23:24 ` Randy.Dunlap [this message]
2004-05-11 2:50 ` Rusty Russell
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=20040510162413.6db2d60e.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=zwane@linuxpower.ca \
/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®