Re: [PATCH] add container release logic - update fc transport to utilize it

[James Bottomley <James.Bottomley@SteelEye.com>]

On Tue, 2007-08-14 at 15:26 -0400, James Smart wrote:
> > 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 ?

Not looping no, but otherwise that's basically correct.

I was thinking of a wait_event driven system checking for
list_empty(cont->containers.k_list)

I'll cook up a patch.

James