![]() | |||||||||||||
Messages in this thread |
On Mon, Jan 08, 2007 at 12:31:44AM -0800, Amit Choudhary wrote: > > --- 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. _Definitely_ cargo-cult programming... - 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/ | ||||||||||||
| Last update: 2007-01-08 09:39 [from the cache] ©2003-2008 | |||||||||||||