From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"hare@suse.com" <hare@suse.com>,
"jthumshirn@suse.de" <jthumshirn@suse.de>,
"ptikhomirov@virtuozzo.com" <ptikhomirov@virtuozzo.com>,
"ncopa@alpinelinux.org" <ncopa@alpinelinux.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] Avoid that ATA error handling hangs
Date: Thu, 22 Feb 2018 03:53:19 +0000 [thread overview]
Message-ID: <1519271598.3258.5.camel@wdc.com> (raw)
In-Reply-To: <1519266202.16203.5.camel@wdc.com>
On Thu, 2018-02-22 at 02:23 +0000, Damien Le Moal wrote:
> On Wed, 2018-02-21 at 09:23 -0800, Bart Van Assche wrote:
> > [ ... ]
> This does not compile.
This patch depends on another patch that is not yet in Martin's tree. See also
https://marc.info/?l=linux-scsi&m=151675130615597. I should have mentioned this
in the patch description.
> Testing this, the rcu hang is now gone.
Thanks for the testing :-)
> However, the behavior of the error recovery is still different from what I
> see in 4.15 and 4.14. For my test case, an unaligned write to a sequential
> zone on a ZAC drive connected to an AHCI port, the report zone issued during
> the disk revalidation after the write error fails with a timeout, which causes
> capacity change to 0, port reset and recovery again. Eventually, everything
> comes back up OK, but it takes some time.
>
> I am investigating to make sure I am not hitting a device FW bug to confirm if
> this is a kernel problem.
This patch was tested with the SRP protocol. I'm not an ATA expert but I hope
that someone who is more familiar with ATA than I can chime in.
Bart.
next prev parent reply other threads:[~2018-02-22 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 17:23 [PATCH] Avoid that ATA error handling hangs Bart Van Assche
2018-02-22 2:23 ` Damien Le Moal
2018-02-22 3:53 ` Bart Van Assche [this message]
2018-02-22 4:06 ` Martin K. Petersen
2018-02-22 4:19 ` Damien Le Moal
2018-02-22 4:39 ` Bart Van Assche
2018-02-22 4:39 ` Bart Van Assche
2018-02-22 4:55 ` Damien Le Moal
2018-02-22 17:15 ` Natanael Copa
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=1519271598.3258.5.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ncopa@alpinelinux.org \
--cc=ptikhomirov@virtuozzo.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