On Wed, Sep 3, 2008 at 12:27 PM, Pekka Enberg <[EMAIL PROTECTED]> wrote: > On Wed, Sep 3, 2008 at 8:08 AM, Steve VanDeBogart > <[EMAIL PROTECTED]> wrote: >> Ideally, we'd tell Valgrind that the bytes of a free'd slab object are >> no longer accessible, but the initialized state should remain the same >> until the object is made accessible again by the next allocation of >> the object. Unfortunately, the compression method for A & V bits in >> Valgrind doesn't allow a region to be inaccessible and retain validness >> bits. > > I don't see why you should mark them initialized all the time. Just > mark them as uninitialized on kmem_cache_free() and again as > initialized when they're about to be returned from kmem_cache_alloc() > like we do in kmemcheck.
Btw, actually, we don't mark them as uninitialized at the moment, but that's a bug in kmemcheck. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
