From: Jens Axboe <axboe@suse.de>
To: Paul Gortmaker <p_gortmaker@yahoo.com>
Cc: torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] off-by-1 error in ide-probe (2.4.x)
Date: Sun, 18 Mar 2001 22:35:58 +0100 [thread overview]
Message-ID: <20010318223558.L29105@suse.de> (raw)
In-Reply-To: <3AB47DA4.795B609B@yahoo.com>
In-Reply-To: <3AB47DA4.795B609B@yahoo.com>; from p_gortmaker@yahoo.com on Sun, Mar 18, 2001 at 04:19:32AM -0500
On Sun, Mar 18 2001, Paul Gortmaker wrote:
> There is a potentially serious bug in ide-probe.c in which max_sectors
> is set to 256 instead of 255. I am surprised that this hasn't bit anyone
> else yet. Perhaps because you need a disk that is slow in comparison to
> the host in order for the queue to climb up to and then hit the 256, at
> which point it then falls over.
You don't need a slow disk, it's trivial to provoke 256 sector sized
request on even the fastest disk available. People hit it all the time,
just with working drives...
> For example, with an old 700MB Maxtor on a "fast" 486, VL-bus, PIO,
> hdparm -c1 -m8 -u1, I could pretty much on demand generate the following
> error by multiple builds, or by the final linking of any big project:
The 256 is _not_ a bug in the driver, it's more likely a bug in your
drive. 256 is a perfectly legal transfer size. That said, maybe it is
a good idea to leave it at 255 just for safety on drives not handling
0 sectors == 128kB transfer.
--
Jens Axboe
next prev parent reply other threads:[~2001-03-18 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-18 9:19 [PATCH] off-by-1 error in ide-probe (2.4.x) Paul Gortmaker
2001-03-18 21:35 ` Jens Axboe [this message]
2001-03-18 23:27 ` Linus Torvalds
2001-03-18 23:32 ` Andre Hedrick
2001-03-22 9:26 ` Paul Gortmaker
2001-03-22 13:32 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2001-03-19 0:18 Andries.Brouwer
2001-03-19 1:24 ` Linus Torvalds
2001-03-19 2:23 ` Andre Hedrick
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=20010318223558.L29105@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
--cc=torvalds@transmeta.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 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.