From: yangxingui <yangxingui@huawei.com>
To: Jason Yan <yanaijie@huawei.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <john.g.garry@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <prime.zeng@hisilicon.com>,
<kangfenglong@huawei.com>
Subject: Re: [PATCH] scsi: libsas: Directly kick-off EH when ATA device fell off
Date: Fri, 16 Dec 2022 17:53:18 +0800 [thread overview]
Message-ID: <ddc08902-cbf1-52c3-e7b0-8c130d4bf58c@huawei.com> (raw)
In-Reply-To: <e717fe34-4448-ab78-7208-71fb1679114e@huawei.com>
On 2022/12/16 17:29, Jason Yan wrote:
> On 2022/12/16 11:29, Xingui Yang wrote:
>> If the ATA device fell off, call sas_ata_device_link_abort() directly and
>> mark all outstanding QCs as failed and kick-off EH Immediately. This
>> avoids
>> having to wait for block layer timeouts.
>>
>> Signed-off-by: Xingui Yang <yangxingui@huawei.com>
>> ---
>> drivers/scsi/libsas/sas_discover.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/scsi/libsas/sas_discover.c
>> b/drivers/scsi/libsas/sas_discover.c
>> index d5bc1314c341..bd22741daa99 100644
>> --- a/drivers/scsi/libsas/sas_discover.c
>> +++ b/drivers/scsi/libsas/sas_discover.c
>> @@ -362,6 +362,11 @@ static void sas_destruct_ports(struct
>> asd_sas_port *port)
>> void sas_unregister_dev(struct asd_sas_port *port, struct
>> domain_device *dev)
>> {
>> + if (test_bit(SAS_DEV_GONE, &dev->state) &&
>> + (dev->dev_type == SAS_SATA_DEV ||
>> + (dev->tproto & SAS_PROTOCOL_STP)))
>
> dev_is_sata() would be better here.
ok, Thanks for your advice.
Thanks,
Xingui
>
> Thanks,
> Jason
>
>> + sas_ata_device_link_abort(dev, false);
>> +
>> if (!test_bit(SAS_DEV_DESTROY, &dev->state) &&
>> !list_empty(&dev->disco_list_node)) {
>> /* this rphy never saw sas_rphy_add */
>>
> .
prev parent reply other threads:[~2022-12-16 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 3:29 [PATCH] scsi: libsas: Directly kick-off EH when ATA device fell off Xingui Yang
2022-12-16 3:53 ` Jason Yan
2022-12-16 7:55 ` yangxingui
2022-12-16 9:29 ` Jason Yan
2022-12-16 9:53 ` yangxingui [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=ddc08902-cbf1-52c3-e7b0-8c130d4bf58c@huawei.com \
--to=yangxingui@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.