linux-kernel - Re: [PATCH] X86: fix typo PAT to 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080118123140.GI11044@elte.hu>
Date:	Fri, 18 Jan 2008 13:31:40 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <Yinghai.Lu@....COM>
Cc:	venkatesh.pallipadi@...el.com, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] X86: fix typo PAT to X86_PAT


* Yinghai Lu <Yinghai.Lu@....COM> wrote:

> > thanks. But, i think we should rather do the following: if X86_PAT 
> > is eanbled then /proc/mtrr should be read-only. There's no problem 
> > _looking_ at MTRR contents, as long as we do not try to modify them. 
> > Hm?
> 
> anyway
> 
> depends on !PAT
> 
> need to be removed.
> 
> it seems when PAT is used, some code still touch MTRR.

you mean modifies MTRRs? Which code is that? (besides the /proc/mtrr 
userspace API)

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