Quoting r. Or Gerlitz <[EMAIL PROTECTED]>: > what about enhancing xxx_destory_id() to sense that it was called from > this id callback context so the xxx module code defers the destory_id() > execution to run after the callback is over. This can be done by > writing at the id the pid of the thread running the callback before > going to the consumer and deleting it when the callback returns. Then if > in_callback(id) holds, have the destory_id() call schedule itself to > later stage, where it checks again etc.
And then you still have the module unloading race. We have the client registration all over the place now - ib_cm was the only one left. -- MST _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
