linux-kernel - Re: [PATCH v9 3/10] x86, asm: Change is_new_memtype

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: <alpine.DEB.2.11.1505220901380.5457@nanos>
Date:	Fri, 22 May 2015 09:02:39 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Toshi Kani <toshi.kani@...com>
cc:	hpa@...or.com, mingo@...hat.com, akpm@...ux-foundation.org,
	arnd@...db.de, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	x86@...nel.org, linux-nvdimm@...1.01.org, jgross@...e.com,
	stefan.bader@...onical.com, luto@...capital.net, hmh@....eng.br,
	yigal@...xistor.com, konrad.wilk@...cle.com, Elliott@...com,
	mcgrof@...e.com, hch@....de
Subject: Re: [PATCH v9 3/10] x86, asm: Change is_new_memtype_allowed() for
 WT

On Wed, 13 May 2015, Toshi Kani wrote:

> __ioremap_caller() calls reserve_memtype() to set new_pcm
> (existing map type if any), and then calls
> is_new_memtype_allowed() to verify if converting to new_pcm
> is allowed when pcm (request type) is different from new_pcm.
> 
> When WT is requested, the caller expects that writes are
> ordered and uncached.  Therefore, this patch changes
> is_new_memtype_allowed() to disallow the following cases.
> 
>  - If the request is WT, mapping type cannot be WB
>  - If the request is WT, mapping type cannot be WC
> 
> Signed-off-by: Toshi Kani <toshi.kani@...com>

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
--
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/