linux-toradex.git/drivers/scsi, branch v3.4

[SCSI] virtio_scsi: fix TMF use-after-free

2012-05-10T07:27:06+00:00

Fix a use-after-free in the TMF path, where cmd may have been already
freed by virtscsi_complete_free when wait_for_completion restarts
executing virtscsi_tmf.  Technically a race, but in practice the command
will always be freed long before the completion waiter is awoken.

The fix is to make callers specifying a completion responsible for
freeing the command in all cases.

Signed-off-by: Hu Tao 
Signed-off-by: Paolo Bonzini 
Signed-off-by: James Bottomley

[SCSI] fix oops in all legacy host adapters caused by 6f381fa

2012-05-10T07:24:13+00:00

Commit 6f381fa344911d5a234b13574433cf23036f9467
Author: Lin Ming 

[SCSI] scsi_lib: use correct DMA device in __scsi_alloc_queue
 
Caused a regression where we oops in every legacy mode SCSI host driver
because they supply a NULL pointer to scsi_add_host().  Fix this by checking
for the NULL in scsi_add_host_with_dma() and changing the DMA device to being
the platform_bus in that case (which replicates the original behaviour).

Reported-by: Al Viro 
Signed-off-by: James Bottomley

[SCSI] qla2xxx: Update version number to 8.04.00.03-k.

2012-05-10T07:19:10+00:00

Signed-off-by: Giridhar Malavali 
Signed-off-by: Chad Dupuis 
Signed-off-by: James Bottomley

[SCSI] qla2xxx: Properly check for current state after the fabric-login request.

2012-05-10T07:18:04+00:00

[jejb: checkpatch fixes]
Signed-off-by: Saurav Kashyap 
Signed-off-by: Chad Dupuis 
Signed-off-by: James Bottomley

[SCSI] qla2xxx: Proper completion to scsi-ml for scsi status task_set_full and busy.

2012-05-10T07:15:19+00:00

In case of firmmware detected under-run condition and scsi status of
task_set_full or busy_condition, return that to the mid layer for proper error
handling instead of DID_ERROR (which causes error handler activation and a
full retry).

Signed-off-by: Giridhar Malavali 
Signed-off-by: Chad Dupuis 
Signed-off-by: James Bottomley

[SCSI] qla2xxx: Block flash access from application when device is initialized for ISP82xx.

2012-05-10T07:10:58+00:00

Signed-off-by: Giridhar Malavali 
Signed-off-by: Chad Dupuis 
Signed-off-by: James Bottomley

[SCSI] qla2xxx: Fix reset time out as qla2xxx not ack to reset request.

2012-05-10T07:07:49+00:00

Signed-off-by: Vikas Chaudhary 
Signed-off-by: Chad Dupuis 
Signed-off-by: James Bottomley

[SCSI] libfc: update mfs boundry checking

2012-04-25T07:46:29+00:00

A previous commit changed the mfs checking to ensure the new
mfs is less or equal to the mfs supported by the FCF. This
doesn't work for BRDCM cards as they set an mfs of 2048 regardless
of whether the switch returns a larger mfs.

This patch validates the new mfs against the upper and lower spec
defined boundries for a FCoE mfs.

Signed-off-by: Vasu Dev 
Signed-off-by: Bhanu Prakash Gollapudi 
Signed-off-by: Robert Love 
Signed-off-by: James Bottomley

[SCSI] Revert "[SCSI] libsas: fix sas port naming"

2012-04-23T11:15:53+00:00

This reverts commit a692b0eec5efae382dfa800e8b4b083f172921a7.

Tom reports:

[    8.741033] ------------[ cut here ]------------
[    8.741038] WARNING: at fs/sysfs/dir.c:508 sysfs_add_one+0xc1/0xf0()
[    8.741040] Hardware name: To Be Filled By O.E.M.
[    8.741041] sysfs: cannot create duplicate filename

...and missing 2 out of 4 drives connected to mvsas.  Commit a692b0ee
made the assumption that all the phy ids an lldd registers to libsas are
unique.  However, in the "multi-chip" case mvsas does a rather annoying
duplication of phy ids in the array passed to libsas.  So, for example,
chip0 has phy0-3 at ha phy index 0-3 and chip1 has its phy0-3 at ha phy
index 4-7.  The more natural model would be to create a scsi_host (and
sas_ha) per chip (controller), but for now revert the naming fix which
unfortunately means dealing with unpredictable end-device names for a
bit longer.

Cc: Xiangliang Yu 
Cc: Patrick Thomson 
Reported-by: Tom Rini 
Tested-by: Tom Rini 
Signed-off-by: Dan Williams 
Signed-off-by: James Bottomley

[SCSI] libsas: fix false positive 'device attached' conditions

2012-04-23T11:14:09+00:00

Normalize phy->attached_sas_addr to return a zero-address in the case
when device-type == NO_DEVICE or the linkrate is invalid to handle
expanders that put non-zero sas addresses in the discovery response:

 sas: ex 5001b4da000f903f phy02:U:0 attached: 0100000000000000 (no device)
 sas: ex 5001b4da000f903f phy01:U:0 attached: 0100000000000000 (no device)
 sas: ex 5001b4da000f903f phy03:U:0 attached: 0100000000000000 (no device)
 sas: ex 5001b4da000f903f phy00:U:0 attached: 0100000000000000 (no device)

Reported-by: Andrzej Jakowski 
Signed-off-by: Dan Williams 
Cc: stable@vger.kernel.org
Signed-off-by: James Bottomley