Mike Christie wrote:
What is the host_lock use for?
With this patch is is still possible for the module to unload right
before lpfc_bsg_request is called? Should this use a try_module_get and
if that fails fail the request?
Why not just add the module get() and put() calls to the fc class (would
it just push the problem up?)?
Or what about in bsg.c, have bsg_open do a module_get? Could we add a
module pointer to the bsg's devices request_queue and have bsg do the
get when the device is opened?
The correct thing to do would be to have bsg_open do a class-object get and
bsg_close a class-object put - whatever object the bsg queue is bound to.
I'll look into what this means (how to get to the object).
-- 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