Re: [PATCH] include/linux/slab.h: new KFREE() macro.

Amit Choudhary
2007-01-08T08:31:46Z

--- Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> On 1/8/07, Hua Zhong <hzhong@gmail.com> wrote:
> > > And as I explained, it can result in longer code too. So, why
> > > keep this value around. Why not re-initialize it to NULL.
> >
> > Because initialization increases code size.
>
> And it also effectively blocks the slab debugging code from doing its
> job detecting double-frees.
>

Man, so you do want someone to set 'x' to NULL after freeing it, so that the slab debugging code
can catch double frees. If you set it to NULL then double free is harmless. So, you want something
harmful in the system and then debug it with the slab debugging code. Man, doesn't make sense to
me.

-Amit

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around