On Wed, 22 Oct 2008, Pekka Enberg wrote:
Actually, when debugging is enabled, it's customary to poison the object, for example (see free_debug_processing() in mm/slub.c). So we really can't "easily ensure" that in the allocator unless we by-pass all the current debugging code.
We may be talking of different frees here. Maybe what he means by freeing is that the object was put on the lru? And we understand a kfree().
-- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
