Re: Valgrind meets UML

Jeff Dike (jdike@karaya.com)
Fri, 20 Dec 2002 17:58:18 -0500


jreiser@BitWagon.com said:
> Implementors of allocators can have bugs in the valgrind declarations
> they add. An "independent" check based on documented
> externally-visible behavior can help.

The problem is that valgrind is going to look under the covers of the kernel
allocators and see the externally-visible requirements being violated.

Either you implement a globally correct description, which includes the
externally visible description as a subset, or you somehow tell valgrind not
to complain about stuff inside the allocator.

The second sounds complicated, and anyway hides bugs in the allocator.

> Nested allocators (inner allocator grabs a large region, outer
> allocator performs sub-allocations of small pieces from the large
> region) can be troublesome.

And are another reason for implementing a globally correct description.

Jeff

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