From: Mark Lord <kernel@teksavvy.com>
To: jgarzik <jgarzik@redhat.com>
Cc: ycbzzjlby <ycbzzjlby@gmail.com>, mlord <mlord@pobox.com>,
linux-ide <linux-ide@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Fix libata-eh don't retry command after reset succeeded.
Date: Mon, 14 Jan 2013 09:01:12 -0500 [thread overview]
Message-ID: <50F40FA8.4070101@teksavvy.com> (raw)
In-Reply-To: <201301141820562689358@gmail.com>
>
> From 9cc9a85f17a8525e53caf430611d762c105d324c Mon Sep 17 00:00:00 2001
> From: Bian Yu <ycbzzjlby@gmail.com>
> Date: Tue, 18 Dec 2012 05:58:34 -0500
> Subject: [PATCH] Fix libata-eh don't retry command after reset succeeded.
> It's introduced by commit 8d899e70c1b3afff, When disk has a UNC error,
> qc->err_mask will set AC_ERR_MEDIA flag.
> Signed-off-by: Bian Yu <ycbzzjlby@gmail.com>
>
> ---
> drivers/ata/libata-eh.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c
> index bf039b0..bcf4437 100644
> --- a/drivers/ata/libata-eh.c
> +++ b/drivers/ata/libata-eh.c
> @@ -2094,7 +2094,7 @@ static unsigned int ata_eh_speed_down(struct ata_device *dev,
> */
> static inline int ata_eh_worth_retry(struct ata_queued_cmd *qc)
> {
> - if (qc->flags & AC_ERR_MEDIA)
> + if (qc->err_mask & AC_ERR_MEDIA)
> return 0; /* don't retry media errors */
> if (qc->flags & ATA_QCFLAG_IO)
> return 1; /* otherwise retry anything from fs stack */
> --
> 1.7.1
Yup, good catch. The original patch to fix retries (from me) had it that way,
but somewhere among the enforced revisions this error crept in unnoticed.
Jeff -- wanna pick this one up?
Could be useful for -stable, too.
next parent reply other threads:[~2013-01-14 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201301141820562689358@gmail.com>
2013-01-14 14:01 ` Mark Lord [this message]
2013-01-14 14:03 ` [PATCH] Fix libata-eh don't retry command after reset succeeded Mark Lord
2013-01-14 17:41 ` Sergei Shtylyov
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=50F40FA8.4070101@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mlord@pobox.com \
--cc=ycbzzjlby@gmail.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