From: yangxingui <yangxingui@huawei.com>
To: John Garry <john.g.garry@oracle.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: Wed, 28 Feb 2024 21:13:51 +0800 [thread overview]
Message-ID: <693dec74-1750-191e-cbc3-37f993d165ac@huawei.com> (raw)
In-Reply-To: <d765d2c5-3451-4519-a5e1-9e8f28dcd6b3@oracle.com>
Hi John,
On 2024/2/22 20:41, John Garry wrote:
> 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.
>
By the way, I have updated a version and call sas_set_ex_phy() here,
please check it again.
Thanks,
Xingui
next prev parent reply other threads:[~2024-02-28 13:13 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
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 [this message]
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=693dec74-1750-191e-cbc3-37f993d165ac@huawei.com \
--to=yangxingui@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=damien.lemoal@opensource.wdc.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=martin.petersen@oracle.com \
--cc=prime.zeng@hisilicon.com \
--cc=yanaijie@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®