James Bottomley wrote:
I'm afraid if you look at your solution, you'll see it still doesn't quite work: If the next thing the user does after unloading lpfc is to unload the transport class, the module is blown away with potentially a live release callback to now freed code.
You're right... Although, most don't as the transports are dependencies for the LLDD's, and it's only the LLDDs they care about. But, point taken.
Isn't a better way to handle it simply to give transport_container_unregister() the semantics everyone is expecting (i.e. to wait for everything to be tidied up and gone)? That way none of the transport classes needs updating, and we don't have to handle the rather nasty release and unload races.
I was hoping you'd give some guidance. This area is black voodoo... :) Sure - so are you suggesting that transport_container_unregister() continually loop until successful ? If not, what other kind of semantic can we give it that we don't have to muck with the transport classes ? -- james s - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
