On Thu, Dec 27, 2007 at 12:28:14PM -0800, Christoph Lameter wrote:
quoted text
> Hmmm.. If I separately allocate the kobject then I can no longer get to 
> the kmem_cache structure from the kobject. 
> 
> I need to add a second kobject_del to sysfs_slab_remove() to make sysfs 
> completely forget about the object?
> 
> Probably should track down any remaining symlinks at that point and nuke 
> them too. Isnt there some way to convince sysfs to remove the symlinks 
> if the target vanishes?

Don't bother with separate allocation.

a) remove symlink when slab goes away
b) instead of kfree() in slab removal do kobject_put() if you have sysfs stuff
c) have ->release() of these kobjects do kfree()
--
unsubscribe notice
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/