From: John Garry <john.g.garry@oracle.com>
To: Xingui Yang <yangxingui@huawei.com>,
yanaijie@huawei.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, damien.lemoal@opensource.wdc.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, prime.zeng@hisilicon.com,
chenxiang66@hisilicon.com, kangfenglong@huawei.com
Subject: Re: [PATCH] scsi: libsas: Fix disk not being scanned in after being removed
Date: Thu, 22 Feb 2024 12:41:15 +0000 [thread overview]
Message-ID: <d765d2c5-3451-4519-a5e1-9e8f28dcd6b3@oracle.com> (raw)
In-Reply-To: <20240221073159.29408-1-yangxingui@huawei.com>
On 21/02/2024 07:31, Xingui Yang wrote:
> As of commit d8649fc1c5e4 ("scsi: libsas: Do discovery on empty PHY to
> update PHY info"), do discovery will send a new SMP_DISCOVER and update
> phy->phy_change_count. We found that if the disk is reconnected and phy
> change_count changes at this time, the disk scanning process will not be
> triggered.
>
> So update the PHY info with the last query results.
>
> Fixes: d8649fc1c5e4 ("scsi: libsas: Do discovery on empty PHY to update PHY info")
> Signed-off-by: Xingui Yang <yangxingui@huawei.com>
> ---
> drivers/scsi/libsas/sas_expander.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/scsi/libsas/sas_expander.c b/drivers/scsi/libsas/sas_expander.c
> index a2204674b680..9563f5589948 100644
> --- a/drivers/scsi/libsas/sas_expander.c
> +++ b/drivers/scsi/libsas/sas_expander.c
> @@ -1681,6 +1681,10 @@ int sas_get_phy_attached_dev(struct domain_device *dev, int phy_id,
> if (*type == 0)
> memset(sas_addr, 0, SAS_ADDR_SIZE);
> }
> +
> + if ((SAS_ADDR(sas_addr) == 0) || (res == -ECOMM))
> + sas_set_ex_phy(dev, phy_id, disc_resp);
> +
> kfree(disc_resp);
> return res;
> }
> @@ -1972,11 +1976,6 @@ static int sas_rediscover_dev(struct domain_device *dev, int phy_id,
> if ((SAS_ADDR(sas_addr) == 0) || (res == -ECOMM)) {
> phy->phy_state = PHY_EMPTY;
> sas_unregister_devs_sas_addr(dev, phy_id, last);
> - /*
> - * Even though the PHY is empty, for convenience we discover
> - * the PHY to update the PHY info, like negotiated linkrate.
> - */
> - sas_ex_phy_discover(dev, phy_id);
It would be nice to be able to call sas_set_ex_phy() here (instead of
sas_get_phy_attached_dev()), but I assume that you can't do that as the
disc_resp memory is not available.
If we were to manually set the PHY info here instead, how would that look?
Thanks,
John
> return res;
> } else if (SAS_ADDR(sas_addr) == SAS_ADDR(phy->attached_sas_addr) &&
> dev_type_flutter(type, phy->attached_dev_type)) {
next prev parent reply other threads:[~2024-02-22 12:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 7:31 Xingui Yang
2024-02-22 12:41 ` John Garry [this message]
2024-02-23 4:04 ` yangxingui
2024-02-23 7:04 ` Jason Yan
2024-02-27 3:06 ` yangxingui
2024-02-27 7:16 ` Jason Yan
2024-02-27 9:06 ` John Garry
2024-02-27 9:42 ` yangxingui
2024-02-28 13:13 ` yangxingui
2024-02-28 16:26 ` John Garry
2024-02-28 18:13 ` John Garry
2024-03-01 1:55 ` Jason Yan
2024-03-04 12:50 ` yangxingui
2024-03-05 2:56 ` Jason Yan
2024-03-05 10:15 ` John Garry
2024-03-05 11:25 ` yangxingui
2024-03-06 17:57 ` John Garry
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=d765d2c5-3451-4519-a5e1-9e8f28dcd6b3@oracle.com \
--to=john.g.garry@oracle.com \
--cc=chenxiang66@hisilicon.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jejb@linux.ibm.com \
--cc=kangfenglong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=prime.zeng@hisilicon.com \
--cc=yanaijie@huawei.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
all inboxes | Powered by JetHome®