linux-kernel - Re: WARNING: kmemcheck: Caught 32-bit read from uninitialized memory (f6f6e1a4), by kmemleak's scan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Aug 2009 10:04:29 +0200
From:	Vegard Nossum <vegard.nossum@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	Catalin Marinas <catalin.marinas@....com>,
	linux-kernel@...r.kernel.org
Subject: Re: WARNING: kmemcheck: Caught 32-bit read from uninitialized memory 
	(f6f6e1a4), by kmemleak's scan_block()

2009/8/25 Ingo Molnar <mingo@...e.hu>:
>
> FYI, -tip testing triggered the following kmemcheck warning in
> kmemleak:
>
> PM: Adding info for No Bus:vcsa7
> WARNING: kmemcheck: Caught 32-bit read from uninitialized memory (f6f6e1a4)
> d873f9f600000000c42ae4c1005c87f70000000070665f666978656400000000
>  i i i i u u u u i i i i i i i i i i i i i i i i i i i i i u u u
>         ^
>
> Pid: 3091, comm: kmemleak Not tainted (2.6.31-rc7-tip #1303) P4DC6
> EIP: 0060:[<c110301f>] EFLAGS: 00010006 CPU: 0
> EIP is at scan_block+0x3f/0xe0
> EAX: f40bd700 EBX: f40bd780 ECX: f16b46c0 EDX: 00000001
> ESI: f6f6e1a4 EDI: 00000000 EBP: f10f3f4c ESP: c2605fcc
>  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> CR0: 8005003b CR2: e89a4844 CR3: 30ff1000 CR4: 000006f0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> DR6: ffff4ff0 DR7: 00000400
>  [<c110313c>] scan_object+0x7c/0xf0
>  [<c1103389>] kmemleak_scan+0x1d9/0x400
>  [<c1103a3c>] kmemleak_scan_thread+0x4c/0xb0
>  [<c10819d4>] kthread+0x74/0x80
>  [<c10257db>] kernel_thread_helper+0x7/0x3c
>  [<ffffffff>] 0xffffffff
> kmemleak: 515 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 42 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>
> config attached. (And this is the first documented case of a kmem
> civil war i guess ;-)

Already the patch to make kmemcheck and kmemleak mutually exclusive is
underway. It is not surprising that kmemleak is scanning uninitialized
memory. But if you say that you have tried it before, it is strange
that it didn't appear until now.

In any case, I don't think it is very productive to run them both at
the same time, simply because kmemcheck slows every memory access down
so much and scanning memory doesn't exactly help that. It _could_ be
useful to have them compiled into the same kernel, though, e.g. a
distro "-debug" kernel.

Maybe you can just add the "depends on !KMEMLEAK" to CONFIG_KMEMCHECK
in tip/out-of-tree for now?


Vegard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/