linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ewan Milne <emilne@redhat.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-scsi@vger.kernel.org, michael.christie@oracle.com,
	 dgilbert@interlog.com, bvanassche@acm.org, hare@suse.de
Subject: Re: [PATCH v4 2/9] scsi: sd: Do not retry ASC 0x3a in read_capacity_10() with any ASCQ
Date: Fri, 3 Oct 2025 10:40:18 -0400	[thread overview]
Message-ID: <CAGtn9rkZX-C7DgaMCABsF66RVGomQeK1RyRW5knLPsPEzvajOA@mail.gmail.com> (raw)
In-Reply-To: <8f250e77-5069-416d-9389-9c3e99535dbc@kernel.org>

On Fri, Oct 3, 2025 at 12:24 AM Damien Le Moal <dlemoal@kernel.org> wrote:
>
> On 10/3/25 04:25, Ewan D. Milne wrote:
> > This makes the handling in read_capacity_10() consistent with other
> > cases, e.g. sd_spinup_disk().  Omitting .ascq in scsi_failure did not
> > result in wildcard matching, it only handled ASCQ 0x00.  This patch
> > changes the retry behavior, we no longer retry 3 times on ASC 0x3a
> > if a nonzero ASCQ is ever returned.
> >
> > Signed-off-by: Ewan D. Milne <emilne@redhat.com>
>
> Doesn't this need a Fixes tag ?

I don't normally add a Fixes: tag for things like this, since I don't know
if any device actually returns a nonzero ASCQ.  (I think either you or
Bart asked for this change in an earlier patch series, which is fine.)

-Ewan

>
> Other than that, looks OK to me.
>
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
>
> --
> Damien Le Moal
> Western Digital Research
>


  reply	other threads:[~2025-10-03 14:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 19:25 [PATCH v4 0/9] Retry READ CAPACITY(10)/(16) with good status but no data Ewan D. Milne
2025-10-02 19:25 ` [PATCH v4 1/9] scsi: Explicitly specify .ascq = 0x00 for ASC 0x28/0x29 scsi_failures Ewan D. Milne
2025-10-03  4:24   ` Damien Le Moal
2025-10-06  6:59   ` Hannes Reinecke
2025-10-02 19:25 ` [PATCH v4 2/9] scsi: sd: Do not retry ASC 0x3a in read_capacity_10() with any ASCQ Ewan D. Milne
2025-10-03  4:24   ` Damien Le Moal
2025-10-03 14:40     ` Ewan Milne [this message]
2025-10-03 15:44       ` Bart Van Assche
2025-10-03 18:40         ` Ewan Milne
2025-10-06 17:54           ` Bart Van Assche
2025-10-02 19:25 ` [PATCH v4 3/9] scsi: sd: Have scsi-ml retry read_capacity_16 errors Ewan D. Milne
2025-10-06  2:00   ` Damien Le Moal
2025-10-06  7:01   ` Hannes Reinecke
2025-10-02 19:25 ` [PATCH v4 4/9] scsi: sd: Avoid passing potentially uninitialized "sense_valid" to read_capacity_error() Ewan D. Milne
2025-10-06  2:02   ` Damien Le Moal
2025-10-06  7:06   ` Hannes Reinecke
2025-10-02 19:25 ` [PATCH v4 5/9] scsi: sd: Remove checks for -EOVERFLOW in sd_read_capacity() Ewan D. Milne
2025-10-06  2:04   ` Damien Le Moal
2025-10-06  7:07   ` Hannes Reinecke
2025-10-02 19:25 ` [PATCH v4 6/9] scsi: sd: Check for and retry in case of READ_CAPCITY(10)/(16) returning no data Ewan D. Milne
2025-10-06  2:06   ` Damien Le Moal
2025-10-06  7:10   ` Hannes Reinecke
2025-10-06  7:20     ` Damien Le Moal
2025-10-06  7:25       ` Damien Le Moal
2025-10-06 10:59         ` Hannes Reinecke
2025-10-02 19:25 ` [PATCH v4 7/9] scsi: Simplify nested if conditional in scsi_probe_lun() Ewan D. Milne
2025-10-06  2:07   ` Damien Le Moal
2025-10-06  7:11   ` Hannes Reinecke
2025-10-02 19:25 ` [PATCH v4 8/9] scsi: scsi_debug: Add option to suppress returned data but return good status Ewan D. Milne
2025-10-06  2:09   ` Damien Le Moal
2025-10-06  7:12   ` Hannes Reinecke
2025-10-02 19:25 ` [PATCH v4 9/9] scsi: scsi_debug: Add "only_once" module option to inject an error one time Ewan D. Milne
2025-10-06  2:12   ` Damien Le Moal
2025-10-06  7:12   ` Hannes Reinecke

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=CAGtn9rkZX-C7DgaMCABsF66RVGomQeK1RyRW5knLPsPEzvajOA@mail.gmail.com \
    --to=emilne@redhat.com \
    --cc=bvanassche@acm.org \
    --cc=dgilbert@interlog.com \
    --cc=dlemoal@kernel.org \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michael.christie@oracle.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;
as well as URLs for NNTP newsgroup(s).