From: Jason Yan <yanaijie@huawei.com>
To: Xingui Yang <yangxingui@huawei.com>, <john.g.garry@oracle.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <liyihang9@h-partners.com>,
<liuyonglong@huawei.com>, <kangfenglong@huawei.com>
Subject: Re: [PATCH] Revert "scsi: libsas: Fix exp-attached device scan after probe failure scanned in again after probe failed"
Date: Thu, 27 Nov 2025 15:21:43 +0800 [thread overview]
Message-ID: <19929526-cc46-4337-b6e2-5305002565a4@huawei.com> (raw)
In-Reply-To: <20251021073438.3441934-1-yangxingui@huawei.com>
在 2025/10/21 15:34, Xingui Yang 写道:
> 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@huawei.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);
> - }
You need to track probe failed times, and if probe failed more than 3
times, stop trying to probe this phy.
Jaosn
祝一切顺利
> -
> sas_unregister_dev(dev->port, dev);
> }
>
prev parent reply other threads:[~2025-11-27 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 7:34 [PATCH] Revert "scsi: libsas: Fix exp-attached device scan after probe failure scanned in again after probe failed" Xingui Yang
2025-11-27 0:59 ` yangxingui
2025-11-27 6:47 ` John Garry
2025-11-27 7:27 ` yangxingui
2025-12-01 12:51 ` John Garry
2025-12-01 13:27 ` Jason Yan
2025-12-02 7:00 ` yangxingui
2025-11-27 7:21 ` Jason Yan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19929526-cc46-4337-b6e2-5305002565a4@huawei.com \
--to=yanaijie@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=john.g.garry@oracle.com \
--cc=kangfenglong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=liyihang9@h-partners.com \
--cc=martin.petersen@oracle.com \
--cc=yangxingui@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox