From: Tejun Heo <tj@kernel.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
"\"linux-ide@vger.kernel.org\" st" <linux-ide@vger.kernel.org>,
stable <stable@kernel.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Milan Kocian <milan.kocian@wq.cz>
Subject: Re: [PATCH #upstream-fixes] pata_cmd64x: revert commit d62f5576
Date: Tue, 17 Aug 2010 17:01:10 +0200 [thread overview]
Message-ID: <4C6AA436.2090003@kernel.org> (raw)
In-Reply-To: <201008171456.43648.bzolnier@gmail.com>
Hello,
On 08/17/2010 02:56 PM, Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 17 August 2010 02:13:42 pm Tejun Heo wrote:
>> Commit d62f5576 (pata_cmd64x: fix handling of address setup timings)
>> incorrectly called ata_timing_compute() on UDMA mode on 0 @UT leading
>> to devide by zero fault. Revert it until better fix is available.
>> This is reported in bko#16607 by Milan Kocian who also root caused it.
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=16607
>
> How's about giving the ATA maintainer some time to resolve the issue
> properly?
Yeap, sure.
> The revert should be a last resort action (+ the issue was reported
> only yesterday) as it introduces another regression (it just replaces
> new bug with the old bug while adding noise in the process)..
The old problem is much less severe tho. The introduced regression
causes oops while the old bug probably doesn't show itself too often.
Does it really need to merge the DMA timings too? If the device can't
do certain timing, it's PIO configuration should reflect that so
merging PIO part only should be enough for PIO configuration, no?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-08-17 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 12:13 [PATCH #upstream-fixes] pata_cmd64x: revert commit d62f5576 Tejun Heo
2010-08-17 12:56 ` Bartlomiej Zolnierkiewicz
2010-08-17 15:01 ` Tejun Heo [this message]
2010-08-17 15:39 ` Alan Cox
2010-08-17 16:39 ` Bartlomiej Zolnierkiewicz
2010-08-17 17:41 ` Sergei Shtylyov
2010-08-17 21:30 ` Jeff Garzik
2010-08-19 10:30 ` Milan Kocian
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=4C6AA436.2090003@kernel.org \
--to=tj@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=milan.kocian@wq.cz \
--cc=stable@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