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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1251208658.15678.45.camel@pc1117.cambridge.arm.com>
Date:	Tue, 25 Aug 2009 14:57:38 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	Vegard Nossum <vegard.nossum@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: WARNING: kmemcheck: Caught 32-bit read from uninitialized
	memory (f6f6e1a4), by kmemleak's scan_block()

On Tue, 2009-08-25 at 12:43 +0200, Ingo Molnar wrote:
> btw., i re-tested the original tree, and got the lockup/crash below.
> 
> 	Ingo
> 
> --------------->
> EXT3 FS on sdb1, internal journal
> EXT3-fs: mounted filesystem with writeback data mode.
> BUG: soft lockup - CPU#0 stuck for 61s! [kmemleak:3080]

Do you have the "Allow rescheduling during object scanning" patch? Apart
from that, you may need another for not holding the tasklist_lock when
scanning the task stacks - it is at the top of my kmemleak branch,
together with a patch or informing kmemleak about thread stack
allocations
(http://www.linux-arm.org/git?p=linux-2.6.git;a=shortlog;h=refs/heads/kmemleak).

With these patches, I don't get any soft lockups on my system.

-- 
Catalin

--
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/