From: John Garry <john.g.garry@oracle.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Jason Yan <yanaijie@huawei.com>,
Xingui Yang <yangxingui@huawei.com>,
jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-ide@vger.kernel.org, hare@suse.com, hch@lst.de
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, prime.zeng@hisilicon.com,
kangfenglong@huawei.com
Subject: Re: [PATCH V2] scsi: libsas: Directly kick-off EH when ATA device fell off
Date: Tue, 20 Dec 2022 08:43:31 +0000 [thread overview]
Message-ID: <12cf34d6-8267-ac81-02c4-190bb9afc50b@oracle.com> (raw)
In-Reply-To: <4489f80f-9f39-8f3f-5d10-6b113131e65c@opensource.wdc.com>
On 19/12/2022 23:00, Damien Le Moal wrote:
>> But it is expected that ata_qc_issue() should be called with that the
>> host lock grabbed (and keep it).
>>
>> I think that the reason libsas drops the lock is because some LLDD
>> queuecommand CBs calls task_done() in some error paths. If we kept the
>> lock held, then we could have a deadlock, for example:
>>
>> sas_ata_qc_issue (has lock) -> lldd_execute_task() =
>> pm8001_queue_command() -> task_done() = sas_ata_task_done() -> grab host
>> lock => deadlock.
> That should be easily solvable using a workqueue for doing task_done(), no ?
>
I don't see why we cannot just return an error code directly from the
lldd_execute_task CB always - we end up calling scsi_done() directly
then. But I am suspicious why it is not already done this way.
Looking at the code history, this fiddling with the ap->lock actually
looks related to commit 312d3e56119a4bc5c36a96818f87f650c069ddc2
("[SCSI] libsas: remove ata_port.lock management duties from lldds"). I
will check that further.
Thanks,
John
next prev parent reply other threads:[~2022-12-20 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221216100327.7386-1-yangxingui@huawei.com>
2022-12-19 9:23 ` [PATCH V2] scsi: libsas: Directly kick-off EH when ATA device fell off John Garry
2022-12-19 12:59 ` yangxingui
2022-12-19 14:53 ` John Garry
2022-12-20 2:34 ` yangxingui
2022-12-20 9:49 ` Jason Yan
2022-12-21 9:40 ` John Garry
2022-12-21 10:29 ` Jason Yan
2022-12-21 9:28 ` yangxingui
2022-12-19 15:28 ` Jason Yan
2022-12-19 15:55 ` John Garry
2022-12-19 23:00 ` Damien Le Moal
2022-12-20 8:43 ` John Garry [this message]
2022-12-19 22:59 ` Damien Le Moal
2022-12-20 2:39 ` Jason Yan
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=12cf34d6-8267-ac81-02c4-190bb9afc50b@oracle.com \
--to=john.g.garry@oracle.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=kangfenglong@huawei.com \
--cc=linux-ide@vger.kernel.org \
--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