From: Catalin Marinas <catalin.marinas@arm.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: kallsyms broken on ARM by commit 17b1f0d
Date: Mon, 15 Jun 2009 13:47:43 +0100 [thread overview]
Message-ID: <1245070063.16986.22.camel@pc1117.cambridge.arm.com> (raw)
Hi Mike,
With the above commit, kallsyms on ARM no longer show correct
information. That's a trace with this commit:
[<c007bfec>] _etext+0xffd9bfec/0x126d8
[<c00795e4>] _etext+0xffd995e4/0x126d8
[<c0147d94>] _etext+0xffe67d94/0x126d8
[<c0147f10>] _etext+0xffe67f10/0x126d8
[<c01481bc>] _etext+0xffe681bc/0x126d8
[<c0148218>] _etext+0xffe68218/0x126d8
[<c0143db0>] _etext+0xffe63db0/0x126d8
[<c0143e18>] _etext+0xffe63e18/0x126d8
[<c007f250>] _etext+0xffd9f250/0x126d8
[<c007c238>] _etext+0xffd9c238/0x126d8
[<c007c2b8>] _etext+0xffd9c2b8/0x126d8
[<c0023dc0>] _etext+0xffd43dc0/0x126d8
and with the commit reverted:
[<c007bfec>] kmemleak_alloc+0x14c/0x260
[<c00795e4>] kmem_cache_alloc+0xd4/0x108
[<c0147d94>] tty_ldisc_try_get+0x18/0xb0
[<c0147f10>] tty_ldisc_get+0x18/0x40
[<c01481bc>] tty_ldisc_reinit+0x28/0x5c
[<c0148218>] tty_ldisc_release+0x28/0x3c
[<c0143db0>] tty_release_dev+0x3cc/0x428
[<c0143e18>] tty_release+0xc/0x14
[<c007f250>] __fput+0x104/0x1c4
[<c007c238>] filp_close+0x70/0x7c
[<c007c2b8>] sys_close+0x74/0xa8
[<c0023dc0>] ret_fast_syscall+0x0/0x28
Any idea what went wrong? I haven't looked at your commit in detail.
Thanks.
--
Catalin
next reply other threads:[~2009-06-15 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 12:47 Catalin Marinas [this message]
2009-06-15 12:51 ` Mike Frysinger
2009-06-15 13:16 ` Catalin Marinas
2009-06-15 13:26 ` Sam Ravnborg
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=1245070063.16986.22.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vapier@gentoo.org \
/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®