On Wed, 30 Oct 2013, Greg KH wrote:
> > I suggest that you implement a function kobject_put_free, that decrements > > the kobject reference count and waits until others stop using the kobject > > and the reference count drops to zero. Then, you change drivers to use > > kobject_put_free instead of kobject_put in their unload routine - that > > will fix this sort of module unload races. > > The "module unload" issue is rare, thankfully, but yes, this type of > function will be showing up in 3.13-rc1 through the btrfs tree as it > needs that functionality, so feel free to use it to resolve this issue > if you need it. > > thanks, > > greg k-h With CONFIG_DEBUG_KOBJECT_RELEASE this issue is not rare - CONFIG_DEBUG_KOBJECT_RELEASE deliberately provokes it. Nice to hear that it will be fixed. You should patch other drivers to use this new function in the unload routine as well. What is the name of the function? I didn't find it in linux-btrfs.git or btrfs-next.git. Mikulas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
