Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 20 Aug 2018 16:26:32 -0700
From: Dave Hansen <>
To: David Woodhouse <>, Tycho Andersen <>,
 Linus Torvalds <>
Cc: Konrad Rzeszutek Wilk <>,,, Jim Mattson <>,
 Andrew Cooper <>,
 Linux Kernel Mailing List <>,
 Boris Ostrovsky <>, linux-mm <>,
 Thomas Gleixner <>,,, Andi Kleen <>,
 Khalid Aziz <>,,
 Liran Alon <>, Kees Cook <>,,
 Kernel Hardening <>,, Tyler Hicks <>,
 John Haxby <>, Jon Masters <>
Subject: Re: Redoing eXclusive Page Frame Ownership (XPFO) with isolated CPUs
 in mind (for KVM to isolate its guests per CPU)

On 08/20/2018 04:14 PM, David Woodhouse wrote:
> If you need the physmap, then rather than manually mapping with 4KiB
> pages, you just switch. Having first ensured that no malicious guest or
> userspace is running on a sibling, of course.

The problem is determining when "you need the physmap".  Tycho's
patches, as I remember them basically classify pages between being
"user" pages which are accessed only via kmap() and friends and "kernel"
pages which need to be mapped all the time because they might have a
'task_struct' or a page table or a 'struct file'.

You're right that we could have a full physmap that we switch to for
kmap()-like access to user pages.  But, the real problem is
transitioning pages from kernel to user usage since it requires shooting
down the old kernel mappings for those pages in some way.

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.