linux-kernel - Re: [GIT PULL] Page Table Isolation (PTI) v4.14 backporting base tree

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 17 Dec 2017 14:05:48 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        "H. Peter Anvin" <hpa@...or.com>, Dave Hansen <dave@...1.net>,
        Borislav Petkov <bp@...en8.de>,
        Andy Lutomirski <luto@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] Page Table Isolation (PTI) v4.14 backporting base tree

Ok, so I've pulled the two prep trees, since they are obviously safe
and don't change any code.

I'm going to read through the actual real changes again one more time
today, but as mentioned, I almost certainly won't actually pull them
until after rc4. I'd like to have at least one calm rc here.

But as part of this all, _please_ make these prep pulls actually work
out - even if you end up having more work in the actual x86 entry tree
and the eventual PTI changes themselves, make sure they really are
based on this, and contain no  more games. I was already a bit dubious
about the whole "let's cherry-pick and then merge to have a common
point", I'm going to be _really_ annoyed if we then need even more odd
games here.

So keep that common point as the common point, and no more backport
games or odd back-merges.

              Linus