linux-kernel - Re: PAT support for i386 and x86

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>] [day] [month] [year] [list]

Date:	Wed, 8 Aug 2007 18:00:39 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Cédric Augonnet <cedric.augonnet@...il.com>
Cc:	Andi Kleen <andi@...stfloor.org>, Loic Prylli <loic@...i.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>, brice@...i.com,
	cedric.augonnet@...-lyon.org
Subject: Re: PAT support for i386 and x86_64

On Wed, Aug 08, 2007 at 11:42:17AM -0400, Cédric Augonnet wrote:
> changing this register is absolutely not the actual issue with PAT, but
> don't
> you think such a first step is needed to avoid conflicts since people _do_
> already set that register from their driver.

Which drivers do that? Ok, I know the ATI 3d driver does, but if that
crashes the users know who is to blame.

No, I don't think we should merge a potentially data corrupting "first
step.". Even first steps have to meet some standards.

> Of course there is no problem for that being dependant on a CONFIG_PAT.

I don't think a CONFIG_DATA_CORRUPTION is a good idea.

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