summaryrefslogtreecommitdiffstats
path: root/drivers/char
diff options
context:
space:
mode:
authorTejun Heo2009-07-15 10:11:41 +0200
committerJeff Garzik2009-07-29 03:07:09 +0200
commit5920dadfb4aec6c1372c5570e71bcd3b4837e63c (patch)
tree4d4e1c5a47d23b1578bfde9ab223b07206a77c64 /drivers/char
parentlibata: Updates and fixes for pata_at91 driver (diff)
downloadkernel-qcow2-linux-5920dadfb4aec6c1372c5570e71bcd3b4837e63c.tar.gz
kernel-qcow2-linux-5920dadfb4aec6c1372c5570e71bcd3b4837e63c.tar.xz
kernel-qcow2-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 'drivers/char')
0 files changed, 0 insertions, 0 deletions