From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Uwe Koziolek <uwe.koziolek@gmx.net>
Subject: Re: [PATCH #upstream] sata_sis: convert to slave_link
Date: Tue, 08 Sep 2009 21:19:25 -0400 [thread overview]
Message-ID: <4AA7029D.1000804@garzik.org> (raw)
In-Reply-To: <4A9D2D5E.90209@kernel.org>
On 09/01/2009 10:19 AM, Tejun Heo wrote:
> During introduction of slave_link, sata_sis slipped through the crack
> and left with ad-hoc merged SCR access. As SCR status was shared for
> both the master and slave devices, when only one of the device is
> online, libata EH would think both are online but would only get valid
> device signature for the actually present one, which in turn trigger
> the probing safety net mechanism and make EH retry causing large delay
> during boot. This patch converts sata_sis to slave_link mechanism.
>
> This bug was reported by TAXI in bko#14075.
>
> http://bugzilla.kernel.org/show_bug.cgi?id=14075
>
> Signed-off-by: Tejun Heo<tj@kernel.org>
> Reported-by: TAXI<taxi@a-city.de>
> Cc: Uwe Koziolek<uwe.koziolek@gmx.net>
> ---
> This is fairly straight-forward fix but I couldn't test it extensively
> and it's way too late in the rc cycle. I think it would be best to
> put it in #upstream and let it see some testing in linux-next and then
> backport them through -stable.
>
> Thanks.
>
> drivers/ata/sata_sis.c | 75 ++++++++++++++++---------------------------------
> 1 file changed, 25 insertions(+), 50 deletions(-)
applied
prev parent reply other threads:[~2009-09-09 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 14:19 [PATCH #upstream] sata_sis: convert to slave_link Tejun Heo
2009-09-09 1:19 ` 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=4AA7029D.1000804@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
--cc=uwe.koziolek@gmx.net \
/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).