IDE disk and HPA
Hello,
I have a question concerning the handling of HPA (Host-protected areas) in current Linux kernels.
Have a look at drivers/ide/ide-disk.c:
static inline void idedisk_check_hpa(ide_drive_t *drive)
{
unsigned long long capacity, set_max;
int lba48 = idedisk_supports_lba48(drive->id);
capacity = drive->capacity64;
if (lba48)
set_max = idedisk_read_native_max_address_ext(drive);
else
set_max = idedisk_read_native_max_address(drive);
if (set_max <= capacity)
return;
printk(KERN_INFO "%s: Host Protected Area detected.\n"
"\tcurrent capacity is %llu sectors (%llu MB)\n"
"\tnative capacity is %llu sectors (%llu MB)\n",
drive->name,
capacity, sectors_to_MB(capacity),
set_max, sectors_to_MB(set_max));
if (lba48)
set_max = idedisk_set_max_address_ext(drive, set_max);
else
set_max = idedisk_set_max_address(drive, set_max);
if (set_max) {
drive->capacity64 = set_max;
printk(KERN_INFO "%s: Host Protected Area disabled.\n",
drive->name);
}
}Do I interpret it right that the following is done in the above function:
1.) The current capacity of the disk is detected.
2.) The "native max. address size" of the disk is detected and stored in set_max.
3.) If capacity < set_max then it is rightly stated that an HPA is detected. 4.) If an HPA is detected, then that HPA is disabled, i.e. the maximum address size is set to the "native max. address size". Afterwards, the HPA is no more!
My question is now: why is an HPA disabled i.e. disprotected when detected? Why not let the HPA alone, because a certain set of disk sectors shall not be accessible by the OS?
Best regards
Oliver
Signature · 12 lines
Acid -- better living through chemistry.
--
__
________________________________________creating IT solutions
Dr. Oliver Tennert
Senior Solutions Engineer
CAx Professional Services
science + computing ag
phone +49(0)7071 9457-598 Hagellocher Weg 71-75
fax +49(0)7071 9457-411 D-72070 Tuebingen, Germany
[email protected] www.science-computing.deQuoted 1 line
Do I interpret it right that the following is done in the above function:
Aside from the version in most kernels being buggy yes
Quoted 3 lines
My question is now: why is an HPA disabled i.e. disprotected when detected? Why not let the HPA alone, because a certain set of disk sectors shall not be accessible by the OS?
Because the HPA is most commonly used to hide all but a fraction of a disk to work with older BIOSes.
Quoted 10 lines · Alan Cox
Quoted 1 line
Do I interpret it right that the following is done in the above function:
Aside from the version in most kernels being buggy yes
Quoted 3 lines
My question is now: why is an HPA disabled i.e. disprotected when detected? Why not let the HPA alone, because a certain set of disk sectors shall not be accessible by the OS?
Because the HPA is most commonly used to hide all but a fraction of a disk to work with older BIOSes.
But as to my knowledge, the HPA was had been introduced to allow HW vendors to store things like diagnostic programs in a part of the disk protected from partitioning and filesystems. The point is, IF there is an HPA, there MIGHT be a partitioning scheme and some filesystems on the disk which rely on the size of disk being the native size MINUS the HPA.
Also there might be some contents in the HPA which is vulnerable to deletion if exposed to the OS in such a transparent way.
So unconditionally disabling the HPA seems not an unconditionally good idea to me.
Why is the HPA not just left alone?
Best regards
Oliver
Signature · 14 lines
"She said, `I know you ... you cannot sing'. I said, `That's nothing,
you should hear me play piano.'"
-- Morrisey
--
__
________________________________________creating IT solutions
Dr. Oliver Tennert
Senior Solutions Engineer
CAx Professional Services
science + computing ag
phone +49(0)7071 9457-598 Hagellocher Weg 71-75
fax +49(0)7071 9457-411 D-72070 Tuebingen, Germany
[email protected] www.science-computing.deQuoted 3 lines · Oliver Tennert
partitioning and filesystems. The point is, IF there is an HPA, there MIGHT be a partitioning scheme and some filesystems on the disk which rely on the size of disk being the native size MINUS the HPA.
Thats fine, Linux is quite happy with such a partitioning table.
Quoted 2 lines
Also there might be some contents in the HPA which is vulnerable to deletion if exposed to the OS in such a transparent way.
By opening the raw disk file yes, but that is not a big concern
Quoted 1 line
Why is the HPA not just left alone?
As I said before - because in most cases the HPA is used just to fool an old bios into booting a large disk.