linux-kernel - Re: HPA patches

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4608A4F4.1010208@garzik.org>
Date:	Tue, 27 Mar 2007 01:00:36 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org, kyle@...onical.com
Subject: Re: HPA patches

Matthew Garrett wrote:
> On Fri, Mar 23, 2007 at 07:13:21PM +0000, Alan Cox wrote:
>> +static int ata_ignore_hpa = 0;
>> +module_param_named(ignore_hpa, ata_ignore_hpa, int, 0644);
>> +MODULE_PARM_DESC(ignore_hpa, "Ignore HPA (0=off 1=on)");
> 
> I'm not sure I like the language here. "Ignore HPA" appears to mean 
> "Explicitly disable the HPA", which I guess is one interpretation of 
> "ignore" - however, naively I'd expect "Ignore HPA" to mean "Don't touch 
> the HPA" with the result that it would remain inaccessible to userspace.

"ignore" sounds more appropriate to me.

We're not just making it inaccessible, we are actively ignoring all 
traces of its existence everywhere, when that setting is enabled.

	Jeff



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