From: Yihang Li <liyihang9@huawei.com>
To: Damien Le Moal <dlemoal@kernel.org>,
<James.Bottomley@HansenPartnership.com>,
<martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<bvanassche@acm.org>, <linuxarm@huawei.com>,
<prime.zeng@huawei.com>, <stable@vger.kernel.org>,
<liyihang9@huawei.com>
Subject: Re: [PATCH v4] scsi: sd: retry command SYNC CACHE if format in progress
Date: Mon, 19 Aug 2024 14:44:37 +0800 [thread overview]
Message-ID: <676e37ba-a9c3-3d52-5c3b-0fa86cf1402e@huawei.com> (raw)
In-Reply-To: <a3fc662c-fa98-4a6e-807b-babb9a344904@kernel.org>
On 2024/8/19 12:17, Damien Le Moal wrote:
> On 8/19/24 13:07, Yihang Li wrote:
>>
>>
>> On 2024/8/19 7:55, Damien Le Moal wrote:
>>> On 8/17/24 10:50, Yihang Li wrote:
>>>> If formatting a suspended disk (such as formatting with different DIF
>>>> type), the disk will be resuming first, and then the format command will
>>>> submit to the disk through SG_IO ioctl.
>>>>
>>>> When the disk is processing the format command, the system does not submit
>>>> other commands to the disk. Therefore, the system attempts to suspend the
>>>> disk again and sends the SYNC CACHE command. However, the SYNC CACHE
>>>
>>> Why would the system try to suspend the disk with a request in flight ? Sounds
>>> like there is a bug with PM reference counting, no ?
>>
>> According to my understand and test, the format command request is finished,
>> so it is not in flight for the kernel. And the command need a few time to processing
>> in the disk while no other commands are being sent.
>
> OK, fine. But I think that retrying SYNC CACHE if the drive is formatting makes
> absolutely no sense at all because there is nothing to flush in that case.
> So what about simply ignoring the error ? I.e. something like this:
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 699f4f9674d9..1da267b8cd8a 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -1824,12 +1824,14 @@ static int sd_sync_cache(struct scsi_disk *sdkp)
> /* this is no error here */
> return 0;
> /*
> - * This drive doesn't support sync and there's not much
> - * we can do because this is called during shutdown
> - * or suspend so just return success so those operations
> - * can proceed.
> + * If a format is in progress (asc = LOGICAL UNIT NOT
> + * READY, ascq = FORMAT IN PROGRESS) or if the drive
> + * does not support sync, there is not much we can do
> + * because this is called during shutdown or suspend. So
> + * just return success so those operations can proceed.
> */
> - if (sshdr.sense_key == ILLEGAL_REQUEST)
> + if ((sshdr.asc == 0x04 && sshdr.ascq == 0x04) ||
> + sshdr.sense_key == ILLEGAL_REQUEST)
> return 0;
> }
>
Thanks for your suggestion, it seems like good.
I will send a new version based on this later.
Thanks,
Yihang.
prev parent reply other threads:[~2024-08-19 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 1:50 [PATCH v4] scsi: sd: retry command SYNC CACHE if format in progress Yihang Li
2024-08-18 23:55 ` Damien Le Moal
2024-08-19 4:07 ` Yihang Li
2024-08-19 4:17 ` Damien Le Moal
2024-08-19 6:44 ` Yihang Li [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=676e37ba-a9c3-3d52-5c3b-0fa86cf1402e@huawei.com \
--to=liyihang9@huawei.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=dlemoal@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@huawei.com \
--cc=stable@vger.kernel.org \
/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