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

[Pekka Enberg]

Hi Ingo,

On Tue, Aug 25, 2009 at 11:40 AM, Ingo Molnar<mingo@xxxxxxx> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/