__scsi_device_lookup(9) [centos man page]

__SCSI_DEVICE_LOOKUP(9) 					  SCSI mid layer					   __SCSI_DEVICE_LOOKUP(9)

NAME

       __scsi_device_lookup - find a device given the host (UNLOCKED)

SYNOPSIS

       struct scsi_device * __scsi_device_lookup(struct Scsi_Host * shost, uint channel, uint id, uint lun);

ARGUMENTS

       shost
	   SCSI host pointer

       channel
	   SCSI channel (zero if only one channel)

       id
	   SCSI target number (physical unit number)

       lun
	   SCSI Logical Unit Number

DESCRIPTION

       Looks up the scsi_device with the specified channel, id, lun for a given host. The returned scsi_device does not have an additional
       reference. You must hold the host's host_lock over this call and any access to the returned scsi_device.

NOTE

       The only reason why drivers would want to use this is because they need to access the device list in irq context. Otherwise you really want
       to use scsi_device_lookup instead.

AUTHORS

       James Bottomley <James.Bottomley@hansenpartnership.com>
	   Author.

       Rob Landley <rob@landley.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   __SCSI_DEVICE_LOOKUP(9)

SRP_RECONNECT_RPORT(9)						  SCSI mid layer					    SRP_RECONNECT_RPORT(9)

NAME

       srp_reconnect_rport - reconnect to an SRP target port

SYNOPSIS

       int srp_reconnect_rport(struct srp_rport * rport);

ARGUMENTS

       rport
	   -- undescribed --

DESCRIPTION

       Blocks SCSI command queueing before invoking reconnect such that queuecommand won't be invoked concurrently with reconnect from outside the
       SCSI EH. This is important since a reconnect implementation may reallocate resources needed by queuecommand.

NOTES

       - This function neither waits until outstanding requests have finished nor tries to abort these. It is the responsibility of the reconnect
       function to finish outstanding commands before reconnecting to the target port. - It is the responsibility of the caller to ensure that the
       resources reallocated by the reconnect function won't be used while this function is in progress. One possible strategy is to invoke this
       function from the context of the SCSI EH thread only. Another possible strategy is to lock the rport mutex inside each SCSI LLD callback
       that can be invoked by the SCSI EH (the scsi_host_template.eh_*() functions and also the scsi_host_template.queuecommand function).

AUTHORS

       James Bottomley <James.Bottomley@hansenpartnership.com>
	   Author.

       Rob Landley <rob@landley.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						    SRP_RECONNECT_RPORT(9)