All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	Avri Altman <avri.altman@wdc.com>,
	linux-scsi@vger.kernel.org,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	Bean Huo <beanhuo@micron.com>,
	Stanley Chu <stanley.chu@mediatek.com>,
	Asutosh Das <quic_asutoshd@quicinc.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: ufs: Increase the START STOP UNIT timeout from 1 s to 10 s
Date: Tue, 11 Apr 2023 21:31:50 +0300	[thread overview]
Message-ID: <a71dc651-a306-eebe-968e-0d9e56f44a76@intel.com> (raw)
In-Reply-To: <0c8b4904-31f4-d21a-7554-6525a264293b@acm.org>

On 11/04/23 20:31, Bart Van Assche wrote:
> On 4/11/23 01:39, Adrian Hunter wrote:
>> On 11/04/23 03:11, Bart Van Assche wrote:
>>> One UFS vendor asked to increase the UFS timeout from 1 s to 3 s.
>>> Another UFS vendor asked to increase the UFS timeout from 1 s to 10 s.
>>> Hence this patch that increases the UFS timeout to 10 s. This patch can
>>> cause the total timeout to exceed 20 s, the Android shutdown timeout.
>>> This is fine since the loop around ufshcd_execute_start_stop() exists to
>>> deal with unit attentions and because unit attentions are reported
>>> quickly.
>>>
>>> Fixes: dcd5b7637c6d ("scsi: ufs: Reduce the START STOP UNIT timeout")
>>
>> Did that commit (shown below) actually increase the timeout
>> because the previous commit (8f2c96420c6e) had put
>> "remaining / HZ" when it should have been just "remaining"?
>> Or am I misreading?
>>
>> So maybe it also needs a fixes tag for 8f2c96420c6e.
> 
> Commit 8f2c96420c6e ("scsi: ufs: core: Reduce the power mode change timeout") changed the START STOP UNIT timeout from START_STOP_TIMEOUT into "remaining / HZ" (should have been "remaining") and hence passed a smaller value than intended to scsi_execute(). Commit dcd5b7637c6d changed the timeout from remaining / HZ into one second. Both values are too small. I'm not sure a second Fixes: tag would help since the above Fixes: tag should be sufficient to make this patch land in all relevant stable trees.

It would be better not to assume current stable trees are the only consumers of fixes.  Presumably adding the extra Fixes tag does no harm.


  reply	other threads:[~2023-04-11 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  0:11 [PATCH] scsi: ufs: Increase the START STOP UNIT timeout from 1 s to 10 s Bart Van Assche
2023-04-11  8:39 ` Adrian Hunter
2023-04-11 17:31   ` Bart Van Assche
2023-04-11 18:31     ` Adrian Hunter [this message]
2023-04-12 16:34       ` Bart Van Assche
2023-04-12 17:24         ` Adrian Hunter
2023-04-12 17:31           ` Bart Van Assche

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=a71dc651-a306-eebe-968e-0d9e56f44a76@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=jaegeuk@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=quic_asutoshd@quicinc.com \
    --cc=stanley.chu@mediatek.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.