linux.git/drivers/scsi/device_handler, branch v3.19-rc2

scsi: handle more device handler setup/teardown in common code

2014-11-12T10:19:36+00:00

Move all code to set up and tear down sdev->scsi_dh_data to common code.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Mike Christie 
Reviewed-by: Hannes Reinecke

scsi: device handlers must have attach and detach methods

2014-11-12T10:19:33+00:00

Signed-off-by: Christoph Hellwig 
Reviewed-by: Mike Christie 
Reviewed-by: Hannes Reinecke

scsi: remove struct scsi_dh_devlist

2014-11-12T10:19:29+00:00

All drivers now do their own matching, so there is no more need to expose
a device list as part of the interface.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Mike Christie 
Reviewed-by: Hannes Reinecke

scsi: use container_of to get at device handler private data

2014-11-12T10:19:25+00:00

Signed-off-by: Christoph Hellwig 
Reviewed-by: Mike Christie 
Reviewed-by: Hannes Reinecke

scsi_dh: get module reference outside of device handler

2014-11-12T10:19:22+00:00

We need to grab a reference to the module before calling the attach
routines to avoid a small race vs module removal.  It also cleans up
the code significantly as a side effect.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Mike Christie 
Reviewed-by: Hannes Reinecke

scsi_dh_hp_sw: fix return value on failed allocation

2014-11-12T10:19:17+00:00

Signed-off-by: Christoph Hellwig 
Reviewed-by: Mike Christie 
Reviewed-by: Hannes Reinecke

scsi: TUR path is down after adapter gets reset with multipath

2014-11-10T14:23:27+00:00

This patch fixes an issue with multipath ipr SAS devices which require a
start unit command to be issued following an adapter reset. Without this
patch, paths get marked failed following an adapter reset and since the
error handler never gets invoked to issue the start unit, the paths are
never recovered. Returning FAILED for this case ensures the error
handler wakes up to issue the start unit.

Signed-off-by: Brian King 
Tested-by: Wen Xiong 
Reviewed-by: Hannes Reinecke 
Signed-off-by: Christoph Hellwig

block,scsi: fixup blk_get_request dead queue scenarios

2014-08-28T16:03:46+00:00

The blk_get_request function may fail in low-memory conditions or during
device removal (even if __GFP_WAIT is set). To distinguish between these
errors, modify the blk_get_request call stack to return the appropriate
ERR_PTR. Verify that all callers check the return status and consider
IS_ERR instead of a simple NULL pointer check.

For consistency, make a similar change to the blk_mq_alloc_request leg
of blk_get_request.  It may fail if the queue is dead, or the caller was
unwilling to wait.

Signed-off-by: Joe Lawrence 
Acked-by: Jiri Kosina  [for pktdvd]
Acked-by: Boaz Harrosh  [for osd]
Reviewed-by: Jeff Moyer 
Signed-off-by: Jens Axboe

block: add blk_rq_set_block_pc()

2014-06-06T13:57:37+00:00

With the optimizations around not clearing the full request at alloc
time, we are leaving some of the needed init for REQ_TYPE_BLOCK_PC
up to the user allocating the request.

Add a blk_rq_set_block_pc() that sets the command type to
REQ_TYPE_BLOCK_PC, and properly initializes the members associated
with this type of request. Update callers to use this function instead
of manipulating rq->cmd_type directly.

Includes fixes from Christoph Hellwig  for my half-assed
attempt.

Signed-off-by: Jens Axboe

[SCSI] scsi_dh_alua: ALUA handler attach should succeed while TPG is transitioning

2013-10-25T10:19:33+00:00

During testing, it was discovered that when a device tries to attach to the
alua handler while in TPG state of transitioning, the alua_rtpg function will
wait for it to exit the state before allowing it to continue. As a result, if
the 60 second timeout expires, the alua handler will not attach to the device.

To fix this, I have introduced an input argument to alua_rtpg called
wait_for_transition.  The idea is that it will wait for the transition to
complete before an activation (because the current TPG state has some bearing
in that case), but during a discovery if it is transitioning, it will not
wait, and will store the state as standby for the time being.

I believe the precedent exists for this from commit
c0d289b3e59577532c45ee9110ef81bd7b341272 Since if the device reports a state
of transitioning, it can transition to other more valid states, and it has
been established TPGS is supported on the device, if it is attaching.

Signed-off-by: Sean Stewart 
Acked-by: Hannes Reinecke 
Signed-off-by: James Bottomley