lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 27 Nov 2006 18:56:47 +0100
From:	Andreas Leitgeb <avl@...ic.at>
To:	Alan <alan@...rguk.ukuu.org.uk>
Cc:	avl@...ic.at, linux-kernel@...r.kernel.org
Subject: Re: Allow turning off hpa-checking.

On Mon, Nov 27, 2006 at 04:33:28PM +0000, Alan wrote:
> > So after real remaining capacity has dropped
> > below original capacity,  querying the "native" size still
> > returns the original size, which is no longer physically
> > backed.
> This is incorrect.

Please, also give some hints, what actually falsifies my 
observation-based speculations. I surely don't insist in them
being accurate, but I try to understand what's really going on.

What else (if not sector remapping) could make the "current"
size gradually smaller between reboots. And why is "native"
size still constant?  And why does now even access to the but-last
native sector fail? The explanation with block-reads no longer
works.

> This is a matter for the partitioning tool. You don't know at boot time
> what you wish to do with the HPA so a boot option is inappropriate.

If I boot linux (e.g. from CD) on some precious windows-machine,
I do know that at boot time. Ditto if I connect a foreign
windows-disk in my machine (ata is afaik not yet hot-pluggable),
I'm also bound to know that at boot time.

There are also user-land tools (using ioctl) to manipulate 
this, in case I change my mind lateron.

How should the partitioning tool know, if I want to ignore the
HPA, or respect it (knowing it contains stuff that I might need in
future).  Does there exist any that asks me?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ