On Friday, 22. July 2005 16:47, Alan Cox wrote:
> > Do I interpret it right that the following is done in the above function:
>
> Aside from the version in most kernels being buggy yes
>
> > 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
--
"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.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|