diff options
| author | Kashyap, Desai <kashyap.desai@lsi.com> | 2010-03-09 17:34:13 +0530 |
|---|---|---|
| committer | James Bottomley <James.Bottomley@suse.de> | 2010-04-11 09:23:29 -0500 |
| commit | 1278b11f46d9f34097f44ecc417148f27e8997fe (patch) | |
| tree | 986281490f5692194f64ce6e79aa5580a9f36bb8 /mm/failslab.c | |
| parent | 40956059fb2ef717f1e864a6685e7cd31758fc2b (diff) | |
| download | kernel_samsung_aries-1278b11f46d9f34097f44ecc417148f27e8997fe.zip kernel_samsung_aries-1278b11f46d9f34097f44ecc417148f27e8997fe.tar.gz kernel_samsung_aries-1278b11f46d9f34097f44ecc417148f27e8997fe.tar.bz2 | |
[SCSI] mpt2sas : Device removal algorithm in interrupt context only
external host not connecting after controller reboot: The
problem is : devices are not coming back after having the cable
disconnected then reconnected. The problem is because the
driver/firmware device removal handshake is failing. Due to this failure,
the controller firmware is not sending out device add events when the target
is reconnected. This is root caused to a race in the driver/firmware device
removal algorithm. There is duplicate code in both interrupt and user
context; where target reset is being issue from user context path while
sas_iounit_control(OP_REMOVE) is being sent from interrupt context. An
active target_reset will fail the OP_REMOVE. To fix this problem, the
duplicate code has been removed from user context path.
Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'mm/failslab.c')
0 files changed, 0 insertions, 0 deletions