Re: çå: problem with kmemleak

[ttlxzz ccc]

Hi, Wang and Catalin:

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.
 I do this below
> cat .config | grep STACETRACE
>
> CONFIG_STACKTRACE_SUPPORT=y
> CONFIG_STACKTRACE=y
> CONFIG_USER_STACKTRACE_SUPPORT=y
>
> As you see, the x86_64 architecture supprot stacktrace. But I found
> there's no backtrace yesterday.
> I'll test it again later.
>
> BTW
>
> cat /proc/cpuinfo | grep processor | wc -l
> 8
> cat /proc/cpuinfo | grep model
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz

and My linux version is redhat 3.4.5

Is it a problem of x86_64 architecture or something else? I am really
very Anxious.

Thanks:)

On Fri, May 13, 2011 at 11:58 AM, ttlxzz ccc <boyzccc@xxxxxxxxx> wrote:
> Hi, wang
> I have test kmemleak on the x86 architecture. There is no problem with
> full backtrace.
> But I can't test it on the x86_64 because my test machine is doing
> something else.:(
> But I do this below
> cat .config | grep STACETRACE
>
> CONFIG_STACKTRACE_SUPPORT=y
> CONFIG_STACKTRACE=y
> CONFIG_USER_STACKTRACE_SUPPORT=y
>
> As you see, the x86_64 architecture supprot stacktrace. But I found
> there's no backtrace yesterday.
> I'll test it again later.
>
> BTW
>
> cat /proc/cpuinfo | grep processor | wc -l
> 8
> cat /proc/cpuinfo | grep model
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
> model           : 26
> model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
>
> thank you :)
>
>
> On Thu, May 12, 2011 at 10:49 PM, Américo Wang <xiyou.wangcong@xxxxxxxxx> wrote:
>> On Thu, May 12, 2011 at 10:33 PM, ttlxzz ccc <boyzccc@xxxxxxxxx> wrote:
>>> Thanks for Wangcong
>>>
>>> I have test the kmemleak-test.ko and the result includes no backtrace
>>> except fffffffff, too.
>>> I'm compling the kernel by make menuconfig. :)
>>
>> Odd, this looks like a bug, Cc Catalin Marinas <catalin.marinas@xxxxxxx>
>>
>> I can't reach my test machine right now, I will try this tomorrow.
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/