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

Consistent with the code in the rest of the transports, when the driver module attached or detached to a transport, the transport ignored the statuses from transport_container_register() and transport_container_unregister(). This was particularly bad on the unregister path, because the transport

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

On Thu, 2007-08-16 at 08:16 -0400, James Smart wrote: Consistent with the code in the rest of the transports, when the driver module attached or detached to a transport, the transport ignored the statuses from transport_container_register() and transport_container_unregister(). This was

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

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...