diff options
| author | Moger, Babu <Babu.Moger@netapp.com> | 2012-01-24 20:38:46 (GMT) |
|---|---|---|
| committer | James Bottomley <JBottomley@Parallels.com> | 2012-02-19 14:08:59 (GMT) |
| commit | 2082ebc45af9c9c648383b8cde0dc1948eadbf31 (patch) | |
| tree | 1c010bb75da085c84cf5223035b2624dc6fbd7d6 /crypto | |
| parent | 3384db9eb8b1e4f94a02c2a0ce3c0efe6142f3ba (diff) | |
| download | linux-2082ebc45af9c9c648383b8cde0dc1948eadbf31.tar.xz | |
[SCSI] fix the new host byte settings (DID_TARGET_FAILURE and DID_NEXUS_FAILURE)
This patch fixes the host byte settings DID_TARGET_FAILURE and
DID_NEXUS_FAILURE. The function __scsi_error_from_host_byte, tries to reset
the host byte to DID_OK. But that does not happen because of the OR operation.
Here is the flow.
scsi_softirq_done-> scsi_decide_disposition -> __scsi_error_from_host_byte
Let's take an example with DID_NEXUS_FAILURE. In scsi_decide_disposition,
result will be set as DID_NEXUS_FAILURE (=0x11). Then in
__scsi_error_from_host_byte, when we do OR with DID_OK. Purpose is to reset
it back to DID_OK. But that does not happen. This patch fixes this issue.
Signed-off-by: Babu Moger <babu.moger@netapp.com>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions