From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream 2/2] libata-eh: clear UNIT ATTENTION after reset
Date: Fri, 27 Jun 2008 02:41:27 -0400 [thread overview]
Message-ID: <48648B97.8000409@garzik.org> (raw)
In-Reply-To: <484E4945.3050907@gmail.com>
Tejun Heo wrote:
> Resets make ATAPI devices raise UNIT ATTENTION which fails the next
> command. As resets can happen asynchronously for unrelated reasons,
> this sometimes disrupts innocent users. For example, reading DVD
> fails after the system wakes up from suspend or the other device
> sharing the channel went through bus error.
>
> Clearing UA has some problems as it might clear UA which the userland
> needs to know about. However, UA after resets can only be about the
> reset itself and benefits of clearing it overweights cons. Missing UA
> can only delay failure to one of the following commands anyway. For
> example, timeout while burning is in progress will trigger reset and
> reset the device state and probably corrupt the burning run. Although
> the userland application won't get the UA, its pending writes will
> fail.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> drivers/ata/libata-eh.c | 105 +++++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 99 insertions(+), 6 deletions(-)
ACK, but does not apply to #upstream
next prev parent reply other threads:[~2008-06-27 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 9:28 [PATCH #upstream 1/2] libata-eh: update atapi_eh_request_sense() to take @dev instead of @qc Tejun Heo
2008-06-10 9:28 ` [PATCH #upstream 2/2] libata-eh: clear UNIT ATTENTION after reset Tejun Heo
2008-06-27 6:41 ` Jeff Garzik [this message]
2008-08-30 12:20 ` [PATCH #upstream UPDATED " Tejun Heo
2008-09-29 4:34 ` Jeff Garzik
2008-06-27 6:41 ` [PATCH #upstream 1/2] libata-eh: update atapi_eh_request_sense() to take @dev instead of @qc Jeff Garzik
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=48648B97.8000409@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).