linux-kernel - Re: [PATCH] x86: fixed mtrr change WP to WB

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: <4820A401.1040105@zytor.com>
Date:	Tue, 06 May 2008 11:31:29 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yhlu.kernel@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: fixed mtrr change WP to WB

Yinghai Lu wrote:
>>
>>  If the mptable should be modified, it should be copied to kernel memory and
>> modified there.  Modifying it in-place is both unsafe and, in general,
>> simply will not work.
> 
> but
> 
>          * 1) Scan the bottom 1K for a signature
>          * 2) Scan the top 1K of base RAM
>          * 3) Scan the 64K of bios
>          */
>         if (smp_scan_config(0x0, 0x400, reserve) ||
>             smp_scan_config(639 * 0x400, 0x400, reserve) ||
>             smp_scan_config(0xF0000, 0x10000, reserve))
>                 return;
> 
> and all these areas are reserved already.
> 
> wonder if we could only modify mpf->mpf_physptr to point to another
> mpc and reuse mpf?
> 

Obviously, if you have already modified a table, you should save a 
pointer to it, and not rely on the kernel scanning later.

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