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  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]
Date:   Mon, 20 Aug 2018 16:38:31 -0700
From:   Linus Torvalds <>
To:     Dave Hansen <>
Cc:     David Woodhouse <>,
        Tycho Andersen <>,
        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 Mon, Aug 20, 2018 at 4:27 PM Dave Hansen <> wrote:
> 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.

You might decide that you simply don't care enough, and are willing to
leave possible stale TLB entries rather than shoot things down.

Then you'd still possibly see user pages in the kernel map, but only
for a fairly limited time, and only until the TLB entry gets re-used
for other reasons.

Even with kernel page table entries being marked global, their
lifetime in the TLB is likely not very long, and definitely not long
enough for some user that tries to scan for pages.


Powered by blists - more mailing lists