diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2012-01-31 09:40:45 +0400 |
|---|---|---|
| committer | James Bottomley <JBottomley@Parallels.com> | 2012-03-01 01:42:51 +0400 |
| commit | 26a2e68f816ebd736a0484ca293457b280af4ef1 (patch) | |
| tree | 5fbae208c3bcda21dd1f9f918e811e07c2ce80e8 /crypto/xor.c | |
| parent | 77c309f3cdf9e217032dfe330f5881d352bb0436 (diff) | |
| download | linux-26a2e68f816ebd736a0484ca293457b280af4ef1.tar.xz | |
[SCSI] libsas: don't recover end devices attached to disabled phys
If userspace has decided to disable a phy the kernel should honor that
and not inadvertantly re-enable the phy via error recovery. This is
more straightforward in the sata case where link recovery (via
libata-eh) is separate from sas_task cancelling in libsas-eh. Teach
libsas to accept -ENODEV as a successful response from I_T_nexus_reset
('successful' in terms of not escalating further).
This is a more comprehensive fix then "libsas: don't recover 'gone'
devices in sas_ata_hard_reset()", as it is no longer sata-specific.
aic94xx does check the return value from sas_phy_reset() so if the phy
is disabled we proceed with clearing the I_T_nexus.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
Diffstat (limited to 'crypto/xor.c')
0 files changed, 0 insertions, 0 deletions