From: ttlxzz ccc <boyzccc@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 答复: problem with kmemleak
Date: Sun, 15 May 2011 14:01:47 +0800 [thread overview]
Message-ID: <BANLkTimW+efD9FJzFjCzdSYCYRwAg+ZGtg@mail.gmail.com> (raw)
In-Reply-To: <1305295737.31204.112.camel@e102109-lin.cambridge.arm.com>
Hi, Catalin=:)
I enable CONFIG_BACKTRACE_SELF_TEST and check the log
vim /var/log/kernel
and find the backtrace testing below:
May 15 13:48:54 db-sat-test05 kernel: ====[ backtrace testing ]===========
May 15 13:48:54 db-sat-test05 kernel: Testing a backtrace from process context.
May 15 13:48:54 db-sat-test05 kernel: The following trace is a kernel
self test and not a bug!
May 15 13:48:54 db-sat-test05 kernel: Pid: 1, comm: swapper Not
tainted 2.6.32_1-1-0-0 #7
May 15 13:48:54 db-sat-test05 kernel: Call Trace:
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8108b5f9>] ?
backtrace_regression_test+0x50/0x16a
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8117b143>] ?
proc_create_data+0xb3/0xe5
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8182d6e1>] ?
kallsyms_init+0x0/0x30
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8182d706>] ?
kallsyms_init+0x25/0x30
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff81009094>] ?
do_one_initcall+0x6c/0x1c0
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8181133a>] ?
kernel_init+0x2f5/0x381
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8100ca9a>] ? child_rip+0xa/0x20
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff81811045>] ?
kernel_init+0x0/0x381
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8100ca90>] ? child_rip+0x0/0x20
May 15 13:48:54 db-sat-test05 kernel: Testing a backtrace from irq context.
May 15 13:48:54 db-sat-test05 kernel: The following trace is a kernel
self test and not a bug!
May 15 13:48:54 db-sat-test05 kernel: Pid: 22, comm: ksoftirqd/6 Not
tainted 2.6.32_1-1-0-0 #7
May 15 13:48:54 db-sat-test05 kernel: Call Trace:
May 15 13:48:54 db-sat-test05 kernel: <IRQ> [<ffffffff8108b595>] ?
backtrace_test_irq_callback+0xd/0x21
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8105744e>] ?
tasklet_action+0x95/0xf8
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff81057034>] ?
__do_softirq+0xa9/0x154
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff81057892>] ?
ksoftirqd+0x0/0x16c
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8100cb9c>] ?
call_softirq+0x1c/0x28
May 15 13:48:54 db-sat-test05 kernel: <EOI> [<ffffffff8100e8c1>] ?
do_softirq+0x47/0xbc
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff81057917>] ?
ksoftirqd+0x85/0x16c
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8106b6e8>] ? kthread+0x9b/0xaa
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8100ca9a>] ? child_rip+0xa/0x20
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8106b64d>] ? kthread+0x0/0xaa
May 15 13:48:54 db-sat-test05 kernel: [<ffffffff8100ca90>] ? child_rip+0x0/0x20
May 15 13:48:54 db-sat-test05 kernel: Testing a saved backtrace.
May 15 13:48:54 db-sat-test05 kernel: The following trace is a kernel
self test and not a bug!
May 15 13:48:54 db-sat-test05 kernel: [<ffffffffffffffff>] 0xffffffffffffffff
May 15 13:48:54 db-sat-test05 kernel: ====[ end of backtrace testing ]====
Is there something wrong with the backtrace testing so that I can't
get the full backtrace, plz?
thank you very much:)
On Fri, May 13, 2011 at 10:08 PM, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> On Fri, 2011-05-13 at 10:32 +0100, ttlxzz ccc wrote:
>> I have tested kmemleak on the x86 and x86_64 architecture again. There
>> is only
>> backtrace:
>>
>> [<ffffffffffffffff>] 0xffffffffffffffff
>>
>> unreferenced object 0xffffc90012d27000 (size 64):
>>
>> comm "insmod", pid 13092, jiffies 4298369684
>>
>> hex dump (first 32 bytes):
>>
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>
>> backtrace:
>>
>> [<ffffffffffffffff>] 0xffffffffffffffff
>>
>> But in the x86, there is full backtrace.
>
> Can you enable CONFIG_BACKTRACE_SELF_TEST and check whether the
> boot-time backtrace test goes ok?
>
> --
> Catalin
>
>
>
next prev parent reply other threads:[~2011-05-15 6:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 2:06 ttlxzz ccc
2011-05-12 3:13 ` ttlxzz ccc
2011-05-12 9:44 ` Maxin B John
2011-05-12 9:59 ` 答复: " chenxi
2011-05-12 11:16 ` Daniel Baluta
2011-05-12 12:01 ` ttlxzz ccc
2011-05-12 14:18 ` Américo Wang
2011-05-12 14:33 ` ttlxzz ccc
2011-05-12 14:49 ` Américo Wang
2011-05-12 15:00 ` Daniel Baluta
2011-05-12 15:04 ` Catalin Marinas
2011-05-12 15:09 ` ttlxzz ccc
[not found] ` <BANLkTik6c8-g8FrXZy8-V35W6-Th++5p_A@mail.gmail.com>
2011-05-13 9:32 ` ttlxzz ccc
2011-05-13 14:08 ` Catalin Marinas
2011-05-15 6:01 ` ttlxzz ccc [this message]
2011-05-16 7:18 ` ttlxzz ccc
2011-05-16 8:53 ` Catalin Marinas
2011-05-16 8:58 ` Américo Wang
2011-05-12 10:04 ` ttlxzz ccc
2011-05-12 13:52 ` ttlxzz ccc
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=BANLkTimW+efD9FJzFjCzdSYCYRwAg+ZGtg@mail.gmail.com \
--to=boyzccc@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.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®