On Wed, Jun 12, 2013 at 07:41:15PM -0700, Tejun Heo wrote: > Hello, > > On Wed, Jun 12, 2013 at 7:38 PM, Kent Overstreet <koverstreet@xxxxxxxxxx> wrote: > > IMO, list_del() is preferred when the object shouldn't be reused (i.e. > > it gets taken off a list and then it's freed). list_del_init() could > > hide bugs. > > Nah... use-after-frees are detected much more reliably by poisoning > anyway. Using list_del() instead of list_del_init() to hunt down > use-after-free isn't a good idea because you're likely to corrupt the > memory of unrelated area. I really don't see much point in using > list_del(). list_del() does do poisoning - and list debugging is cheaper to enable than full slab debugging. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
