From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, zwane@linuxpower.ca
Subject: Re: [PATCH*] show last kernel-image symbol in /proc/kallsyms
Date: Mon, 10 May 2004 10:56:06 -0700 [thread overview]
Message-ID: <20040510105606.27554ad0.rddunlap@osdl.org> (raw)
In-Reply-To: <1084162450.8121.6.camel@bach>
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. :)
'patch' complains about a malformed input file (the @@ line counts
don't match the patch content).
Correction is below. Or were more patch lines needed (& missing)?
| Name: Show Last Symbol in /proc/kallsyms
| Status: Tested on 2.6.6-rc3.bk11
|
| The current code doesn't show the last symbol (usually _einittext) in
| /proc/kallsyms. The reason for this is subtle: s_start() returns an
| empty string for position 0 (ignored by s_show()), and s_next()
| returns the first symbol for position 1.
|
| What should happen is that update_iter() for position 0 should fill in
| the first symbol. Unfortunately, the get_ksymbol_core() fills in the
| symbol information, *and* updates the iterator: we have to split these
| functions, which we do by making it return the length of the name
| offset.
|
| Then we can call get_ksymbol_core() without moving the iterator,
| meaning that we can call it at position 0 (ie. s_start()).
|
| diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal linux-2.6.6-rc3-bk11/kernel/kallsyms.c working-2.6.6-rc3-bk11/kernel/kallsyms.c
| --- linux-2.6.6-rc3-bk11/kernel/kallsyms.c 2004-03-12 07:57:28.000000000 +1100
| +++ working-2.6.6-rc3-bk11/kernel/kallsyms.c 2004-05-10 13:11:06.000000000 +1000
| @@ -210,16 +212,16 @@ static int update_iter(struct kallsym_it
***** should be: @@ -210,9 +212,10 @@
|
| /* We need to iterate through the previous symbols: can be slow */
| for (; iter->pos != pos; iter->pos++) {
| - get_ksymbol_core(iter);
| + iter->nameoff += get_ksymbol_core(iter);
| cond_resched();
| }
| + get_ksymbol_core(iter);
| return 1;
| }
|
--
~Randy
(Again. Sometimes I think ln -s /usr/src/linux/.config .signature) -- akpm
next prev parent reply other threads:[~2004-05-10 18:04 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 [this message]
2004-05-10 23:24 ` Randy.Dunlap
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=20040510105606.27554ad0.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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®