From: Mark Lord <kernel@teksavvy.com>
To: IDE/ATA development list <linux-ide@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <htejun@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ric Wheeler <rwheeler@redhat.com>
Subject: [PATCH] Fix accesses at LBA28 boundary (old bug, but nasty) (v2)
Date: Wed, 07 Apr 2010 13:52:08 -0400 [thread overview]
Message-ID: <4BBCC648.30807@teksavvy.com> (raw)
In-Reply-To: <4BBBB975.7000203@teksavvy.com>
Most drives from Seagate, Hitachi, and possibly other brands,
do not allow LBA28 access to sector number 0x0fffffff (2^28 - 1).
So instead use LBA48 for such accesses.
This bug could bite a lot of systems, especially when the user has
taken care to align partitions to 4KB boundaries. On misaligned systems,
it is less likely to be encountered, since a 4KB read would end at
0x10000000 rather than at 0x0fffffff.
Signed-off-by: Mark Lord <mlord@pobox.com>
---
Reposting with the pre-existing (u64) cast removed.
--- linux-2.6.34-rc3/include/linux/ata.h 2010-03-30 12:24:39.000000000 -0400
+++ linux/include/linux/ata.h 2010-04-06 18:39:41.167702612 -0400
@@ -1025,8 +1025,8 @@
static inline int lba_28_ok(u64 block, u32 n_block)
{
- /* check the ending block number */
- return ((block + n_block) < ((u64)1 << 28)) && (n_block <= 256);
+ /* check the ending block number: must be LESS THAN 0x0fffffff */
+ return ((block + n_block) < ((1 << 28) - 1)) && (n_block <= 256);
}
static inline int lba_48_ok(u64 block, u32 n_block)
next prev parent reply other threads:[~2010-04-07 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:45 [PATCH] Fix accesses at LBA28 boundary (old bug, but nasty) Mark Lord
2010-04-06 22:47 ` Mark Lord
2010-04-07 1:29 ` Tejun Heo
2010-04-07 3:30 ` Mark Lord
2010-04-07 5:11 ` Tejun Heo
2010-04-07 17:52 ` Mark Lord
2010-04-07 17:52 ` Mark Lord [this message]
2010-04-07 19:18 ` [PATCH] Fix accesses at LBA28 boundary (old bug, but nasty) (v2) Alan Cox
2010-04-07 21:01 ` Tejun Heo
2010-04-08 17:00 ` Jeff Garzik
2010-04-15 13:46 ` Mark Lord
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=4BBCC648.30807@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rwheeler@redhat.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.