Incorporate KAISER patches to Chrome OS 3.8 kernel |
|||||
Issue descriptionFor Meltdown (SSCA variant 3).
,
Feb 3 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/06ba5525027f87f379af9ae1e7e6e0b9c16401cf commit 06ba5525027f87f379af9ae1e7e6e0b9c16401cf Author: Jorge Lucangeli Obes <jorgelo@chromium.org> Date: Fri Feb 02 20:57:25 2018 CHROMIUM: Merge 'kaiser-3.8-tag' into chromeos-3.8 Implement KAISER/KPTI on 3.8 kernels. Changelog: ---------------------------------------------------------------- Andrea Arcangeli (1): BACKPORT: x86/mm/kaiser: re-enable vsyscalls Andy Lutomirski (2): BACKPORT: x86/mm: Enable CR4.PCIDE on supported systems UPSTREAM: x86/mm/64: Fix reboot interaction with CR4.PCIDE Borislav Petkov (1): UPSTREAM: x86/mm: fix bad backport to disable PCID on Xen Hugh Dickins (3): CHROMIUM: KAISER: Kernel Address Isolation CHROMIUM: kaiser: user_map __kprobes_text too CHROMIUM: kaiser: setup_pcid() beware in setting X86_CR4_PCIDE Jorge Lucangeli Obes (2): CHROMIUM: kaiser: Fix kernel_stack. Merge branch 'linux/kaiser-3.8-tag' into merge/chromeos-3.8-kaiser-3.8-tag Kees Cook (1): UPSTREAM: kaiser: Fix build with CONFIG_FUNCTION_GRAPH_TRACER arch/x86/boot/compressed/misc.h | 1 + arch/x86/ia32/ia32entry.S | 7 + arch/x86/include/asm/cpufeature.h | 1 + arch/x86/include/asm/desc.h | 2 +- arch/x86/include/asm/hw_irq.h | 2 +- arch/x86/include/asm/kaiser.h | 126 +++++++++ arch/x86/include/asm/pgtable.h | 18 +- arch/x86/include/asm/pgtable_64.h | 29 +- arch/x86/include/asm/pgtable_types.h | 33 ++- arch/x86/include/asm/processor.h | 4 +- arch/x86/include/asm/tlbflush.h | 72 ++++- arch/x86/include/asm/vsyscall.h | 1 + arch/x86/include/uapi/asm/processor-flags.h | 3 +- arch/x86/kernel/cpu/common.c | 57 +++- arch/x86/kernel/cpu/perf_event_intel_ds.c | 54 +++- arch/x86/kernel/entry_64.S | 101 +++++-- arch/x86/kernel/head_64.S | 24 +- arch/x86/kernel/hpet.c | 3 + arch/x86/kernel/irqinit.c | 2 +- arch/x86/kernel/ldt.c | 16 ++ arch/x86/kernel/process.c | 2 +- arch/x86/kernel/process_64.c | 2 +- arch/x86/kernel/reboot.c | 4 + arch/x86/kernel/vsyscall_64.c | 7 +- arch/x86/kvm/x86.c | 3 +- arch/x86/mm/Makefile | 1 + arch/x86/mm/kaiser.c | 401 ++++++++++++++++++++++++++++ arch/x86/mm/pgtable.c | 31 ++- arch/x86/mm/tlb.c | 41 ++- arch/x86/xen/enlighten.c | 6 + include/asm-generic/vmlinux.lds.h | 7 + include/linux/kaiser.h | 52 ++++ include/linux/mmzone.h | 3 +- include/linux/percpu-defs.h | 32 ++- init/main.c | 2 + kernel/fork.c | 9 +- mm/vmstat.c | 1 + security/Kconfig | 10 + 38 files changed, 1105 insertions(+), 65 deletions(-) create mode 100644 arch/x86/include/asm/kaiser.h create mode 100644 arch/x86/mm/kaiser.c create mode 100644 include/linux/kaiser.h BUG= chromium:807797 TEST=Build and test on various affected systems Signed-off-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Change-Id: Ia8134927121ece9c389c811acb7a4e8e490e2c76
,
Feb 3 2018
,
Mar 8 2018
Given the potential high impact nature of a nefarious actor leveraging the vulnerability this closes up, I believe we should consider bringing this into 65. The patches have been live on 66 for over a month now with no reported negative impact, so the risk here is believed to be low. If this does cause problems in stable promotion we can always revert.
,
Mar 12 2018
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 15 2018
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 15 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bugdroid1@chromium.org
, Feb 2 2018