On Fri, Sep 13, 2013 at 10:00:33AM +0930, Rusty Russell wrote: > Peter Chen <peter.c...@freescale.com> writes: > > Currently, if module's refcount is not zero during the unload, > > it waits there until the user decreases that refcount. > > Hi Peter, > > In practice userspace uses O_NONBLOCK. In fact, I've been > thinking of removing the blocking case altogether, since it's not really > what people want. > > That would solve your problem and make the code simpler. Thoughts? >
So, it will like "Force unload" case, right? If it is the case, it is better have a warning message to indicate some users are still using it, since there may null pointer dereference when the user module has unloaded, and the end user can understand it may be triggered by wrong module unload sequence. Thanks. -- Best Regards, Peter Chen -- 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/
