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: <84144f020908250148x9d6a83ewccf11ef9fc32868a@mail.gmail.com>
Date:	Tue, 25 Aug 2009 11:48:21 +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()

Hi Ingo,

On Tue, Aug 25, 2009 at 11:40 AM, Ingo Molnar<mingo@...e.hu> wrote:
> There's already a couple of exclusion rules in kmemcheck:
>
> menuconfig KMEMCHECK
>        bool "kmemcheck: trap use of uninitialized memory"
>        depends on DEBUG_KERNEL
>        depends on !X86_USE_3DNOW
>        depends on SLUB || SLAB
>        depends on !CC_OPTIMIZE_FOR_SIZE
>        depends on !FUNCTION_TRACER
>
> such type of Kconfig driven exclusion is usually a somewhat lame way
> to express limitations in the software.
>
> CC_OPTIMIZE_FOR_SIZE is an externality that cannot be eliminated,
> but the others could be improved - and we should definitely not
> extend the list of exclusions.

Yup, agreed.
--
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/