diff options
author | jack_wang <jack_wang@usish.com> | 2011-02-19 11:20:53 +0100 |
---|---|---|
committer | James Bottomley <James.Bottomley@suse.de> | 2011-02-28 18:40:34 +0100 |
commit | 183ce896d726fb987da589fa8e36fb7214a494cc (patch) | |
tree | 741d899331336f132274ba2fb116211725d398a2 /drivers/scsi | |
parent | [SCSI] lpfc: block target when port queueing limit is hit (diff) | |
download | linux-183ce896d726fb987da589fa8e36fb7214a494cc.tar.xz linux-183ce896d726fb987da589fa8e36fb7214a494cc.zip |
[SCSI] libsas: fix loopback topology bug during discovery
In some test envirenment, there is loopback topology test. We should
handle this during discovery.
Signed-off-by: Jack Wang <jack_wang@usish.com>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/scsi')
-rw-r--r-- | drivers/scsi/libsas/sas_expander.c | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/drivers/scsi/libsas/sas_expander.c b/drivers/scsi/libsas/sas_expander.c index 505ffe358293..f3f693b772ac 100644 --- a/drivers/scsi/libsas/sas_expander.c +++ b/drivers/scsi/libsas/sas_expander.c @@ -244,6 +244,11 @@ static int sas_ex_phy_discover_helper(struct domain_device *dev, u8 *disc_req, * dev to host FIS as described in section G.5 of * sas-2 r 04b */ dr = &((struct smp_resp *)disc_resp)->disc; + if (memcmp(dev->sas_addr, dr->attached_sas_addr, + SAS_ADDR_SIZE) == 0) { + sas_printk("Found loopback topology, just ignore it!\n"); + return 0; + } if (!(dr->attached_dev_type == 0 && dr->attached_sata_dev)) break; |