Yes.
I'm open to either the scsi_lib helper function, so we have consistent
naming. However, the real answer is to fix bsg to take out references on the
object that registers with bsg - so that driver unload is gated on proper
unregistration, and no outstanding bsg requests. Who knows bsg well enough to
do this ?
-- james s
On 1/18/2012 5:21 PM, Mike Christie wrote:
On 01/18/2012 03:23 PM, James Smart wrote:
> - Create character device to take a reference on the driver (126082)
>
Is this so the driver cannot get unloaded when doing multiple bsg/sysfs
requests? If so having every driver create its own char device seems
wrong. qla2xxx does this too.qla4xxx wants to do it. Every driver has
the problem.
If we do this can we at least have a scsi lib helper function that can
enforce a consistent naming policy for the char devs so userspace apps
do not have to have some crazy look up table for every driver.
Or, is there a better way to support this? Maybe a common sysfs attr on
the host or a bsg request? Something common that works for all drivers
so we do not have to go around to every driver and add char device to them?
--
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
