From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <tj@kernel.org>
Cc: ide <linux-ide@vger.kernel.org>,
stable@kernel.org, Tim Blechmann <tim@klingt.org>
Subject: Re: [PATCH #upstream-fixes] libata: fix incorrect link online check during probe
Date: Tue, 06 Oct 2009 21:03:40 -0400 [thread overview]
Message-ID: <4ACBE8EC.3000609@pobox.com> (raw)
In-Reply-To: <4ACAFB08.8020501@kernel.org>
On 10/06/2009 04:08 AM, Tejun Heo wrote:
> While trying to work around spurious detection retries for
> non-existent devices on slave links, commit
> 816ab89782ac139a8b65147cca990822bb7e8675 incorrectly added link
> offline check logic before ata_eh_thaw() was called. This means that
> if an occupied link goes down briefly at the time that offline check
> was performed, device class will be cleared to ATA_DEV_NONE and libata
> wouldn't retry thus failing detection of the device.
>
> The offline check should be done after the port is thawed together
> with online check so that such link glitches can be detected by the
> interrupt handler and handled properly.
>
> Signed-off-by: Tejun Heo<tj@kernel.org>
> Reported-by: Tim Blechmann<tim@klingt.org>
> Cc: stable@kernel.org
> --
> drivers/ata/libata-eh.c | 50 ++++++++++++++++++++++++++++++------------------
> 1 file changed, 32 insertions(+), 18 deletions(-)
applied. BTW, note your separator lost a dash... it should be three
dashes (---).
next prev parent reply other threads:[~2009-10-07 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 8:08 [PATCH #upstream-fixes] libata: fix incorrect link online check during probe Tejun Heo
2009-10-07 1:03 ` Jeff Garzik [this message]
2009-10-07 6:17 ` Tejun Heo
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=4ACBE8EC.3000609@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tim@klingt.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).