From: tom.leiming@gmail.com (Ming Lei)
To: linux-arm-kernel@lists.infradead.org
Subject: kernel BUG at kernel/kallsyms.c:222!
Date: Mon, 11 Nov 2013 17:57:29 +0800 [thread overview]
Message-ID: <CACVXFVMzOzD+D-MQCUBvC80d4zS-TJfcucKuUvzerGs6gT1fEg@mail.gmail.com> (raw)
In-Reply-To: <CAFRkauCW3FDSuh4t0gvmSWH1m0+qaG0XSoBxmk30Wq1FMy7iFw@mail.gmail.com>
Hi,
On Mon, Nov 11, 2013 at 4:37 PM, Axel Lin <axel.lin@ingics.com> wrote:
> 2013/11/11 Ming Lei <tom.leiming@gmail.com>:
>
> Hi Ming,
>
> commit f6537f2f "scripts/kallsyms: filter symbols not in kernel address space",
> uses CONFIG_PAGE_OFFSET as kernel_start_addr.
> However, for !CONFIG_MMU case we have :
> PAGE_OFFSET != CONFIG_PAGE_OFFSET.
Yes, it is the cause, and strictly speaking, commit f6537f2f is wrong,
but triggered with bogus CONFIG_PAGE_OFFSET if !CONFIG_MMU.
We can fix it either by Rusty's patch or removing the bogus
CONFIG_PAGE_OFFSET for !CONFIG_MMU.
Thanks,
--
Ming Lei
next prev parent reply other threads:[~2013-11-11 9:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1383789208.5970.1.camel@phoenix>
[not found] ` <CACVXFVMn6RSXchQ8u47F35_J+YSnp1bwF1tr-8uCEYwvFsOfgQ@mail.gmail.com>
[not found] ` <CAFRkauAEt-YhBt11opj_GVCLrxGsTSd2LowWGmukTSmGuJkd3A@mail.gmail.com>
2013-11-07 2:36 ` kernel BUG at kernel/kallsyms.c:222! Ming Lei
2013-11-07 2:47 ` Axel Lin
2013-11-07 4:37 ` Ming Lei
2013-11-07 8:36 ` Axel Lin
2013-11-07 23:44 ` Rusty Russell
2013-11-08 0:45 ` Ming Lei
2013-11-08 4:20 ` Axel Lin
2013-11-08 7:13 ` Ming Lei
2013-11-11 0:23 ` Rusty Russell
2013-11-11 6:43 ` Axel Lin
2013-11-11 7:53 ` Ming Lei
2013-11-11 8:37 ` Axel Lin
2013-11-11 9:57 ` Ming Lei [this message]
2013-11-11 10:41 ` Ming Lei
2013-11-11 17:15 ` Jonathan Austin
2013-11-11 19:32 ` Russell King - ARM Linux
2013-11-12 3:22 ` Ming Lei
2013-11-12 17:36 ` Jonathan Austin
2013-11-13 4:41 ` Ming Lei
2013-11-13 9:58 ` Axel Lin
2013-11-13 11:30 ` Ming Lei
2013-12-02 1:57 ` Axel Lin
2013-12-02 2:08 ` Ming Lei
2013-12-10 6:17 ` Rusty Russell
2013-11-11 8:01 ` Uwe Kleine-König
2013-11-08 3:56 ` Axel Lin
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=CACVXFVMzOzD+D-MQCUBvC80d4zS-TJfcucKuUvzerGs6gT1fEg@mail.gmail.com \
--to=tom.leiming@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).