From: "Norman Diamond" <n0diamond@yahoo.co.jp>
To: "Sergei Shtylyov" <sshtylyov@ru.mvista.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-ide@vger.kernel.org>,
"Norman Diamond" <n0diamond@yahoo.co.jp>
Subject: Re: Off-by-one in both LIBATA and IDE drivers
Date: Thu, 12 Mar 2009 06:03:33 +0900 [thread overview]
Message-ID: <065A106FBB5F41B18A030BD2C87570FA@DIAMOND8600> (raw)
In-Reply-To: <49B78859.5050807@ru.mvista.com>
Sergei Shtylyov wrote:
> Norman Diamond wrote:
>> [attribution stolen:]
>>> [Norman Diamond:]
>>>> It looks like both LIBATA and the old IDE drivers
>>>> have an off-by-one error in deciding whether to use
>>>> READ SECTOR(S) instead of READ SECTOR(S) EXT.
>>>>
>>> This was fixed here:
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=97b697a11b07e2ebfa69c488132596cc5eb24119
>>
>> Thank you.
>> I will see if I can port that fix to 2.6.24.3, because
>> Slax 6.0.3 and kernel 2.6.24.3 avoided some other bugs of
>> later kernels.
>
> Note that this doesn't fix it for the IDE core.
That helps explain my subsequent testing. I'm still having problems.
> The ide-disk driver however seems to use LBA48 regardless of the sector
> address.
But that doesn't explain my subsequent testing. That behaviour would cause
it to work in one of my present cases, but it still fails.
> But still there are incorrect capacity checks, and it can fails with
> drivers not supporting LBA48 with DMA...
Yeah that could be part of it. 2.6.20 turned on DMA more often than later
kernels, so I'm now thinking of reverting to 2.6.20. I've heard (but
couldn't test personally) that 2.6.20 gave abysmal performance to users of
AMD chipsets. Since Intel users outnumber them, I'm inclined to revert to a
version that worked for Intel even though AMD suffers.
--------------------------------------
Power up the Internet with Yahoo! Toolbar.
http://pr.mail.yahoo.co.jp/toolbar/
next prev parent reply other threads:[~2009-03-11 21:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 1:50 Norman Diamond
2009-03-11 3:03 ` Jim Paris
2009-03-11 3:28 ` Norman Diamond
[not found] ` <49B78859.5050807@ru.mvista.com>
2009-03-11 21:03 ` Norman Diamond [this message]
2009-03-12 11:20 ` Norman Diamond
2009-03-12 14:30 ` Mark Lord
2009-03-12 23:02 ` Norman Diamond
2009-03-13 7:41 ` Norman Diamond
2009-03-13 14:45 ` Robert Hancock
2009-03-14 2:05 ` Norman Diamond
2009-03-14 2:15 ` Robert Hancock
2009-03-14 8:48 ` Alan Cox
2009-03-14 9:34 ` Norman Diamond
2009-03-14 10:48 ` Alan Cox
2009-03-14 8:46 ` Alan Cox
2009-03-11 8:27 ` Alan Cox
2009-03-11 8:38 ` Norman Diamond
2009-03-12 0:10 ` Robert Hancock
2009-03-12 2:28 ` Norman Diamond
2009-03-12 4:26 ` Robert Hancock
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=065A106FBB5F41B18A030BD2C87570FA@DIAMOND8600 \
--to=n0diamond@yahoo.co.jp \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
/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
all inboxes | Powered by JetHome®