Patch "kaiser: tidied up asm/kaiser.h somewhat" has been added to the 4.4-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
kaiser: tidied up asm/kaiser.h somewhat
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
kaiser-tidied-up-asm-kaiser.h-somewhat.patch
and it can be found in the queue-4.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From foo@baz Wed Jan 3 18:58:12 CET 2018
From: Hugh Dickins <[email protected]>
Date: Sun, 3 Sep 2017 19:18:07 -0700
Subject: kaiser: tidied up asm/kaiser.h somewhat
From: Hugh Dickins <[email protected]>
Mainly deleting a surfeit of blank lines, and reflowing header comment.
--- arch/x86/include/asm/kaiser.h | 32 +++++++++++++------------------- 1 file changed, 13 insertions(+), 19 deletions(-)
arch/x86/include/asm/kaiser.h +13 -19
@@ -1,15 +1,17 @@#ifndef _ASM_X86_KAISER_H#define _ASM_X86_KAISER_H - -/* This file includes the definitions for the KAISER feature. -* KAISER is a counter measure against x86_64 side channel attacks on the kernel virtual memory. -* It has a shodow-pgd for every process. the shadow-pgd has a minimalistic kernel-set mapped, -* but includes the whole user memory. Within a kernel context switch, or when an interrupt is handled, -* the pgd is switched to the normal one. When the system switches to user mode, the shadow pgd is enabled. -* By this, the virtual memory chaches are freed, and the user may not attack the whole kernel memory. +/* +* This file includes the definitions for the KAISER feature. +* KAISER is a counter measure against x86_64 side channel attacks on +* the kernel virtual memory. It has a shadow pgd for every process: the +* shadow pgd has a minimalistic kernel-set mapped, but includes the whole +* user memory. Within a kernel context switch, or when an interrupt is handled, +* the pgd is switched to the normal one. When the system switches to user mode, +* the shadow pgd is enabled. By this, the virtual memory caches are freed, +* and the user may not attack the whole kernel memory. * -* A minimalistic kernel mapping holds the parts needed to be mapped in user mode, as the entry/exit functions -* of the user space, or the stacks. +* A minimalistic kernel mapping holds the parts needed to be mapped in user +* mode, such as the entry/exit functions of the user space, or the stacks. */ #ifdef __ASSEMBLY__#ifdef CONFIG_KAISER
@@ -48,13 +50,10 @@ _SWITCH_TO_KERNEL_CR3 %rax movq PER_CPU_VAR(unsafe_stack_register_backup), %rax .endm - .macro SWITCH_USER_CR3_NO_STACK - movq %rax, PER_CPU_VAR(unsafe_stack_register_backup) _SWITCH_TO_USER_CR3 %rax movq PER_CPU_VAR(unsafe_stack_register_backup), %rax - .endm #else /* CONFIG_KAISER */
@@ -72,7 +71,6 @@ movq PER_CPU_VAR(unsafe_stack_register_b#else /* __ASSEMBLY__ */ -#ifdef CONFIG_KAISER /* * Upon kernel/user mode switch, it may happen that the address
@@ -80,7 +78,6 @@ movq PER_CPU_VAR(unsafe_stack_register_b* stored. To change the address space, another register is * needed. A register therefore has to be stored/restored. */ - DECLARE_PER_CPU_USER_MAPPED(unsigned long, unsafe_stack_register_backup);/**
@@ -95,7 +92,6 @@ DECLARE_PER_CPU_USER_MAPPED(unsigned lon*/ extern int kaiser_add_mapping (unsigned long addr,unsigned long size,unsigned long flags); -/** * kaiser_remove_mapping - unmap a virtual memory part of the shadow mapping * @addr: the start address of the range
@@ -104,12 +100,12 @@ extern int kaiser_add_mapping(unsigned lextern void kaiser_remove_mapping (unsigned long start,unsigned long size);/** -* kaiser_initialize_mapping - Initalize the shadow mapping +* kaiser_init - Initialize the shadow mapping * * Most parts of the shadow mapping can be mapped upon boot * time. Only per-process things like the thread stacks * or a new LDT have to be mapped at runtime. These boot- -* time mappings are permanent and nevertunmapped. +* time mappings are permanent and never unmapped. */ extern void kaiser_init (void );
@@ -117,6 +113,4 @@ extern void kaiser_init(void);#endif /* __ASSEMBLY */ - -#endif /* _ASM_X86_KAISER_H */
Patches currently in stable-queue which might be from [email protected] are
queue-4.4/kaiser-vmstat-show-nr_kaisertable-as-nr_overhead.patch queue-4.4/kaiser-add-nokaiser-boot-option-using-alternative.patch queue-4.4/kaiser-fix-unlikely-error-in-alloc_ldt_struct.patch queue-4.4/kaiser-_pgd_alloc-without-__gfp_repeat-to-avoid-stalls.patch queue-4.4/kaiser-kaiser_flush_tlb_on_return_to_user-check-pcid.patch queue-4.4/x86-paravirt-dont-patch-flush_tlb_single.patch queue-4.4/kaiser-merged-update.patch queue-4.4/kaiser-delete-kaiser_real_switch-option.patch queue-4.4/kaiser-kaiser_remove_mapping-move-along-the-pgd.patch queue-4.4/kaiser-fix-perf-crashes.patch queue-4.4/kaiser-drop-is_atomic-arg-to-kaiser_pagetable_walk.patch queue-4.4/kaiser-load_new_mm_cr3-let-switch_user_cr3-flush-user.patch queue-4.4/kaiser-enhanced-by-kernel-and-user-pcids.patch queue-4.4/kaiser-x86_cr3_pcid_noflush-and-x86_cr3_pcid_user.patch queue-4.4/kaiser-use-alternative-instead-of-x86_cr3_pcid_noflush.patch queue-4.4/kaiser-stack-map-page_size-at-thread_size-page_size.patch queue-4.4/kaiser-name-that-0x1000-kaiser_shadow_pgd_offset.patch queue-4.4/kaiser-fix-regs-to-do_nmi-ifndef-config_kaiser.patch queue-4.4/kaiser-do-not-set-_page_nx-on-pgd_none.patch queue-4.4/kaiser-tidied-up-asm-kaiser.h-somewhat.patch queue-4.4/kaiser-cleanups-while-trying-for-gold-link.patch queue-4.4/kaiser-tidied-up-kaiser_add-remove_mapping-slightly.patch queue-4.4/kaiser-fix-build-and-fixme-in-alloc_ldt_struct.patch queue-4.4/kaiser-kernel-address-isolation.patch queue-4.4/kaiser-enomem-if-kaiser_pagetable_walk-null.patch queue-4.4/kaiser-asm-tlbflush.h-handle-nopge-at-lower-level.patch queue-4.4/kaiser-paranoid_entry-pass-cr3-need-to-paranoid_exit.patch queue-4.4/kaiser-kaiser-depends-on-smp.patch queue-4.4/kaiser-pcid-0-for-kernel-and-128-for-user.patch