linux-kernel - [patch 0/2] x86/mm/pti: Robustness updates

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-next>] [day] [month] [year] [list]

Date:   Wed, 28 Aug 2019 16:24:45 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     x86@...nel.org, Song Liu <songliubraving@...com>,
        Joerg Roedel <jroedel@...e.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Andy Lutomirski <luto@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Rik van Riel <riel@...riel.com>
Subject: [patch 0/2] x86/mm/pti: Robustness updates

Following up on the discussions around the patch Song submitted to 'cure' a
iTLB related performance regression, I picked up Song's patch which makes
clone_page_tables() more robust by handling unaligned addresses proper and
added one which prevents calling into the PTI code when PTI is enabled
compile time, but disabled at runtime (command line or CPU not affected).

There is no point in calling into those PTI functions unconditionally. The
resulting page tables are the same before and after the change which makes
sense as the code clones the kernel page table into the secondary page
table space which is available but not used when PTI is boot time disabled.

But even if it does not do damage today, this could have nasty side effect
when the PTI code is changed, extended etc. later.

Thanks,

	tglx
8<----------------
 pti.c |    8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)