Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 11 Feb 2019 14:59:55 -0800
From: Andy Lutomirski <>
To: Borislav Petkov <>
Cc: Rick Edgecombe <>, Andy Lutomirski <>, 
	Ingo Molnar <>, LKML <>, X86 ML <>, 
	"H. Peter Anvin" <>, Thomas Gleixner <>, Nadav Amit <>, 
	Dave Hansen <>, Peter Zijlstra <>,, 
	linux-integrity <>, 
	LSM List <>, 
	Andrew Morton <>, 
	Kernel Hardening <>, Linux-MM <>, 
	Will Deacon <>, Ard Biesheuvel <>, 
	Kristen Carlson Accardi <>, "Dock, Deneen T" <>
Subject: Re: [PATCH v2 13/20] Add set_alias_ function and x86 implementation

On Mon, Feb 11, 2019 at 11:09 AM Borislav Petkov <> wrote:
> On Mon, Jan 28, 2019 at 04:34:15PM -0800, Rick Edgecombe wrote:
> > This adds two new functions set_alias_default_noflush and
> s/This adds/Add/
> > set_alias_nv_noflush for setting the alias mapping for the page to its
> Please end function names with parentheses, below too.
> > default valid permissions and to an invalid state that cannot be cached in
> > a TLB, respectively. These functions to not flush the TLB.
> s/to/do/
> Also, pls put that description as comments over the functions in the
> code. Otherwise that "nv" as part of the name doesn't really explain
> what it does.
> Actually, you could just as well call the function
> set_alias_invalid_noflush()
> All the other words are written in full, no need to have "nv" there.

Why are you calling this an "alias"?  You're modifying the direct map.
Your patches are thinking of the direct map as an alias of the vmap
mapping, but that does seem a bit backwards.  How about
set_direct_map_invalid_noflush(), etc?


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.