linux-kernel - Re: Allow turning off hpa-checking.

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]

Message-ID: <456C2A6F.9020406@gmail.com>
Date:	Tue, 28 Nov 2006 21:24:15 +0900
From:	Tejun Heo <htejun@...il.com>
To:	avl@...ic.at
CC:	Alan <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: Allow turning off hpa-checking.

Andreas Leitgeb wrote:
[--snip--]
> This theory is backed by my observation of a nearly-broken disk,
> that the quantity "3)" gradually goes down one step after some time.
> The first such step was, when I noticed the problem about half a
> year ago, and just recently it stepped down by another one.

Okay, if that happens on your drive, you gotta burn that foul thing and 
run away as fast/far away as you can.  ;-)

[--snip--]
> The point I'm really trying to make is, that there should be a
> boot option, to disable the query for "1)".  This *must* be a
> boot option, because the querying that I want to be able to
> prevent happens at boot time.
> My broken drive surely doesn't justify the option (or even this
> thread), but the third one of the "uses for 3)" mentioned above
> does. Once the native size is read, I no longer know how many
> sectors were previously "hidden away" by HPA, except by checking
> the kernel-log.
> 
> While Alan has already said, why he thought that this was the
> wrong approach, the reasoning was based on a misunderstanding
> of my question, which I here tried to clear up.

Dunno about IDE layer.  It has been done that way for long time and not 
sure whether adding such option will happen, but for libata, hpa 
handling is still not implemented and it will have to be optional when 
it gets implemented.  So, libata will have such option when it finally 
receives implementation for hpa handling.

-- 
tejun
-
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/