Tejun Heo wrote: > Rusty Russell wrote: >> Now, are you sure that calling cleanup_ccwgroup just after >> device_unregister() works? >> >> static void __exit >> cleanup_ccwgroup (void) >> { >> bus_unregister (&ccwgroup_bus_type); >> } > > It should. After ->exit() is called, there can't be any object left > behind. If a module is hosting objects which can't be destroyed from > ->exit(), its module ref count shouldn't be zero. So, either 1. > refcount != 0 or 2. ->exit() can destroy all objects. As Cornelia > explains, for ccwgroup, it's #1. Note that unload inhibition doesn't > change anything about this.
Hmmm.... There doesn't seem to any reason why the blocking should be after calling ->exit(). And, yeah, it would be more useful and intuitive if blocking happens before ->exit(). What do you think? Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/