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: <84144f020908260348reec91f3v514317f039058d4d@mail.gmail.com>
Date:	Wed, 26 Aug 2009 13:48:41 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	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, Aug 25, 2009 at 12:34 PM, Ingo Molnar<mingo@...e.hu> wrote:
>> On Tue, Aug 25, 2009 at 12:28 PM, Catalin
>> Marinas<catalin.marinas@....com> wrote:
>> >> Does this look OK to you?
>> >
>> > For the kmemleak.c part:
>> >
>> > Acked-by: Catalin Marinas <catalin.marinas@....com>
>>
>> Vegard? Ingo? The patch is based on tip/out-of-tree so it probably
>> should go to the kmemleak tree?
>
> I'm testing it currently - but yeah, i'd agree that it should go
> into the kmemleak tree, with a .32 merge date or so.

Ingo/Vegard, ACK/NAK? I don't want my amazingly good patch to end up
in /dev/null so can we just shove it in kmemleak.git?

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