From: Rusty Russell <rusty@rustcorp.com.au>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix for kallsyms module symbol resolution problem
Date: Mon, 30 Jun 2003 12:06:08 +1000 [thread overview]
Message-ID: <20030630025802.F2F432C232@lists.samba.org> (raw)
In-Reply-To: Your message of "27 Jun 2003 22:26:27 EST." <1056770789.1825.200.camel@mulgrave>
In message <1056770789.1825.200.camel@mulgrave> you write:
> In lots of KALLSYMS symbol resolution in modules, I've noticed the
> appearance of symbols with no names:
>
> Jun 27 20:55:26 raven kernel: [<10131440>] schedule_timeout+0x78/0xdc
> Jun 27 20:55:26 raven kernel: [<000f8240>] +0x4e0/0x598 [sunrpc]
> Jun 27 20:55:26 raven kernel: [<0014504c>] +0x150/0x43c [nfsd]
> Jun 27 20:55:26 raven kernel: [<10109c5c>] ret_from_kernel_thread+0x1c/0x24
>
> The problem seems to be that get_ksymbol doesn't eliminate empty symbol
> names when it does resolution. The attached patch should fix this.
Please test, because that's only one problem.
The other is that the module_text_address() returns true if the value
is within the module, *not* just if it's within a function. So you
can get some noise there, too, on archs which don't do real
backtracing.
Thanks,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-06-30 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 3:26 [PATCH] fix for kallsyms module symbol resolution problem James Bottomley
2003-06-30 2:06 ` Rusty Russell [this message]
2003-06-30 3:13 ` James Bottomley
2003-06-30 6:17 ` Rusty Russell
2003-06-30 14:10 ` James Bottomley
2003-07-01 1:11 ` Rusty Russell
2003-07-01 2:24 ` James Bottomley
2003-07-01 4:58 ` 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=20030630025802.F2F432C232@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=James.Bottomley@steeleye.com \
--cc=kai@tp1.ruhr-uni-bochum.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