[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <88a3dd70-69a7-affd-8495-9333f95350d0@huawei.com>
Date: Thu, 27 Nov 2025 08:59:44 +0800
From: yangxingui <yangxingui@...wei.com>
To: <john.g.garry@...cle.com>, <yanaijie@...wei.com>, <jejb@...ux.ibm.com>,
<martin.petersen@...cle.com>
CC: <linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linuxarm@...wei.com>, <liyihang9@...artners.com>, <liuyonglong@...wei.com>,
<kangfenglong@...wei.com>
Subject: Re: [PATCH] Revert "scsi: libsas: Fix exp-attached device scan after
probe failure scanned in again after probe failed"
Kindly ping for upstream.
On 2025/10/21 15:34, Xingui Yang wrote:
> This reverts commit ab2068a6fb84751836a84c26ca72b3beb349619d.
>
> As the disk may fall into an abnormal loop of probe when it fails to probe
> due to physical reasons and cannot be repaired.
>
> Signed-off-by: Xingui Yang <yangxingui@...wei.com>
> ---
> drivers/scsi/libsas/sas_internal.h | 14 --------------
> 1 file changed, 14 deletions(-)
>
> diff --git a/drivers/scsi/libsas/sas_internal.h b/drivers/scsi/libsas/sas_internal.h
> index 03d6ec1eb970..85948963fb97 100644
> --- a/drivers/scsi/libsas/sas_internal.h
> +++ b/drivers/scsi/libsas/sas_internal.h
> @@ -145,20 +145,6 @@ static inline void sas_fail_probe(struct domain_device *dev, const char *func, i
> func, dev->parent ? "exp-attached" :
> "direct-attached",
> SAS_ADDR(dev->sas_addr), err);
> -
> - /*
> - * If the device probe failed, the expander phy attached address
> - * needs to be reset so that the phy will not be treated as flutter
> - * in the next revalidation
> - */
> - if (dev->parent && !dev_is_expander(dev->dev_type)) {
> - struct sas_phy *phy = dev->phy;
> - struct domain_device *parent = dev->parent;
> - struct ex_phy *ex_phy = &parent->ex_dev.ex_phy[phy->number];
> -
> - memset(ex_phy->attached_sas_addr, 0, SAS_ADDR_SIZE);
> - }
> -
> sas_unregister_dev(dev->port, dev);
> }
>
>
Powered by blists - more mailing lists