diff options
| author | Mark Lord <kernel@teksavvy.com> | 2010-04-07 13:52:08 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2010-05-12 15:02:49 -0700 |
| commit | fdeddaaa28f22a68a14a8e7daed118ea6bd8b6bd (patch) | |
| tree | 2112283578fc570e8ec51f6f63d5509985f2804b /include/media | |
| parent | 9ffd6e94b8029e8d6f64a6172461bc65df87a8b5 (diff) | |
| download | kernel-crypto-fdeddaaa28f22a68a14a8e7daed118ea6bd8b6bd.tar.gz kernel-crypto-fdeddaaa28f22a68a14a8e7daed118ea6bd8b6bd.tar.xz kernel-crypto-fdeddaaa28f22a68a14a8e7daed118ea6bd8b6bd.zip | |
libata: Fix accesses at LBA28 boundary (old bug, but nasty) (v2)
commit 45c4d015a92f72ec47acd0c7557abdc0c8a6499d upstream.
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>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'include/media')
0 files changed, 0 insertions, 0 deletions