summaryrefslogtreecommitdiffstats
path: root/include/linux/libata.h
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2009-07-15 17:11:41 +0900
committerJeff Garzik <jgarzik@redhat.com>2009-07-28 21:07:09 -0400
commit5920dadfb4aec6c1372c5570e71bcd3b4837e63c (patch)
tree4d4e1c5a47d23b1578bfde9ab223b07206a77c64 /include/linux/libata.h
parent7d084d96fdf1d791cb171da57efc1ca89d68dd6c (diff)
downloadlinux-5920dadfb4aec6c1372c5570e71bcd3b4837e63c.tar.gz
linux-5920dadfb4aec6c1372c5570e71bcd3b4837e63c.tar.bz2
linux-5920dadfb4aec6c1372c5570e71bcd3b4837e63c.zip
libata: accept late unlocking of HPA
On certain configurations, HPA isn't or can't be unlocked during probing but it somehow ends up unlocked afterwards. In the following thread, the problem can be reliably reproduced after resuming from STR. The BIOS turns on HPA during boot but forgets to do it during resume. http://thread.gmane.org/gmane.linux.kernel/858310 This patch updates libata revalidation such that it considers native n_sectors. If the device size has increased to match native n_sectors, it's assumed that HPA has been unlocked involuntarily and the device is recognized as the same one. This should be fairly safe while nicely working around the problem. Signed-off-by: Tejun Heo <tj@kernel.org> Reported-by: Christof Warlich <christof@warlich.name> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Diffstat (limited to 'include/linux/libata.h')
-rw-r--r--include/linux/libata.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/libata.h b/include/linux/libata.h
index 79b6d7fd4ac2..e5b6e33c6571 100644
--- a/include/linux/libata.h
+++ b/include/linux/libata.h
@@ -589,6 +589,7 @@ struct ata_device {
#endif
/* n_sector is CLEAR_BEGIN, read comment above CLEAR_BEGIN */
u64 n_sectors; /* size of device, if ATA */
+ u64 n_native_sectors; /* native size, if ATA */
unsigned int class; /* ATA_DEV_xxx */
unsigned long unpark_deadline;