From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Hannes Reinecke <hare@kernel.org>,
"kernel-team@fb.com" <kernel-team@fb.com>
Subject: Re: [PATCH] libata: don't request sense data on !ZAC ATA devices
Date: Mon, 24 Jun 2019 20:27:02 +0000 [thread overview]
Message-ID: <BN8PR04MB5812F774A3C047B8899AD4A1E7E00@BN8PR04MB5812.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20190624163250.GP657710@devbig004.ftw2.facebook.com
On 2019/06/25 1:33, Tejun Heo wrote:
> ZAC support added sense data requesting on error for both ZAC and ATA
> devices. This seems to cause erratic error handling behaviors on some
> SSDs where the device reports sense data availability and then
> delivers the wrong content making EH take the wrong actions. The
> failure mode was sporadic on a LITE-ON ssd and couldn't be reliably
> reproduced.
>
> There is no value in requesting sense data from non-ZAC ATA devices
> while there's a significant risk of introducing EH misbehaviors which
> are difficult to reproduce and fix. Let's do the sense data dancing
> only for ZAC devices.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: Hannes Reinecke <hare@kernel.org>
> ---
> drivers/ata/libata-eh.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c
> index 9d687e1d4325..3bfd9da58473 100644
> --- a/drivers/ata/libata-eh.c
> +++ b/drivers/ata/libata-eh.c
> @@ -1469,7 +1469,7 @@ static int ata_eh_read_log_10h(struct ata_device *dev,
> tf->hob_lbah = buf[10];
> tf->nsect = buf[12];
> tf->hob_nsect = buf[13];
> - if (ata_id_has_ncq_autosense(dev->id))
> + if (dev->class == ATA_DEV_ZAC && ata_id_has_ncq_autosense(dev->id))
> tf->auxiliary = buf[14] << 16 | buf[15] << 8 | buf[16];
>
> return 0;
> @@ -1716,7 +1716,8 @@ void ata_eh_analyze_ncq_error(struct ata_link *link)
> memcpy(&qc->result_tf, &tf, sizeof(tf));
> qc->result_tf.flags = ATA_TFLAG_ISADDR | ATA_TFLAG_LBA | ATA_TFLAG_LBA48;
> qc->err_mask |= AC_ERR_DEV | AC_ERR_NCQ;
> - if ((qc->result_tf.command & ATA_SENSE) || qc->result_tf.auxiliary) {
> + if (dev->class == ATA_DEV_ZAC &&
> + ((qc->result_tf.command & ATA_SENSE) || qc->result_tf.auxiliary)) {
> char sense_key, asc, ascq;
>
> sense_key = (qc->result_tf.auxiliary >> 16) & 0xff;
> @@ -1770,10 +1771,11 @@ static unsigned int ata_eh_analyze_tf(struct ata_queued_cmd *qc,
> }
>
> switch (qc->dev->class) {
> - case ATA_DEV_ATA:
> case ATA_DEV_ZAC:
> if (stat & ATA_SENSE)
> ata_eh_request_sense(qc, qc->scsicmd);
> + /* fall through */
> + case ATA_DEV_ATA:
> if (err & ATA_ICRC)
> qc->err_mask |= AC_ERR_ATA_BUS;
> if (err & (ATA_UNC | ATA_AMNF))
>
For NCQ commands, I believe it is mandatory to request sense data for the failed
command to get the device out of error mode. So isn't this approach breaking
anything for well behaving drives ? Wouldn't it be better to blacklist the
misbehaving SSD you observed the problem with ?
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2019-06-24 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 16:32 [PATCH] libata: don't request sense data on !ZAC ATA devices Tejun Heo
2019-06-24 20:27 ` Damien Le Moal [this message]
2019-06-24 20:57 ` Tejun Heo
2019-06-24 21:59 ` Damien Le Moal
2019-06-25 6:05 ` Hannes Reinecke
2019-06-25 12:25 ` Damien Le Moal
2019-06-25 15:35 ` Jens Axboe
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=BN8PR04MB5812F774A3C047B8899AD4A1E7E00@BN8PR04MB5812.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=hare@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).