linux-kernel - Re: mtrr madness

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

Message-ID: <48BC2405.9070403@shaw.ca>
Date:	Mon, 01 Sep 2008 11:19:01 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Lukas Hejtmanek <xhejtman@....muni.cz>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: mtrr madness

Lukas Hejtmanek wrote:
> Hello,
> 
> it seems that all linux kernels contain a bug with mtrr:
> 
>  cat /proc/mtrr 
> reg00: base=0x00000000 (   0MB), size=198656MB: write-back, count=1
> reg01: base=0x80000000 (2048MB), size=197120MB: write-back, count=1
> reg02: base=0x9fc00000 (2556MB), size=196612MB: uncachable, count=1
> reg03: base=0x100000000 (4096MB), size=200704MB: write-back, count=1
> reg04: base=0x200000000 (8192MB), size=204800MB: write-back, count=1
> 
> (watch the size)
> 
> it is definitely  present in the kernels 2.6.16, 2.6.24, 2.6.25, 2.6.26.
> 
> 198656 is 0x3080000000, the correct value would be 0x80000000, similarly
> 197120 is 0x3020000000, the correct would be 0x20000000. 

Those are set up by the BIOS, so it would be what's at fault. I think we 
may be adding something to fix this up though?
--
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/