From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Robert Hancock <hancockr@shaw.ca>
Subject: Re: [PATCH #upstream-fixes] libata: don't normalize UNKNOWN to NONE after reset
Date: Thu, 10 Jan 2008 16:55:48 -0500 [thread overview]
Message-ID: <47869464.3030301@garzik.org> (raw)
In-Reply-To: <47835DD4.4000609@gmail.com>
Tejun Heo wrote:
> After non-classifying reset, ehc->classes[] could contain
> ATA_DEV_UNKNOWN which used to be normalized to ATA_DEV_NONE for
> consistency. However, this causes unfortunate side effect for drivers
> which have non-classifying hardresets (e.g. sata_nv) by making
> hardreset report ATA_DEV_NONE for non-classifying resets and thus
> makes EH believe that the port is unoccupied and recovery can be
> skipped. The end result is that after a device is swapped with
> another one, the new device isn't attached after the old one is
> detached.
>
> This patch makes ata_eh_reset() not normalize UNKNOWN to NONE after
> non-classifying resets. This fixes the above problem. As UNKNOWN and
> NONE are handled differently by only EH hotplug logic, this doesn't
> cause other behavior changes.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Robert Hancock <hancockr@shaw.ca>
> ---
> Robert, missing new device was a bug in core EH logic not sata_nv.
> BTW, I did quite a few hotplug tests with adma=0 and it works just
> fine. No lock up.
>
> drivers/ata/libata-eh.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
applied
prev parent reply other threads:[~2008-01-10 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 11:26 [PATCH #upstream-fixes] libata: don't normalize UNKNOWN to NONE after reset Tejun Heo
2008-01-10 21:55 ` Jeff Garzik [this message]
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=47869464.3030301@garzik.org \
--to=jeff@garzik.org \
--cc=hancockr@shaw.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.