[GIT PULL] Page Table Isolation (PTI) v4.14 backporting base tree

mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed

From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	"H. Peter Anvin" <hpa@zytor.com>, Dave Hansen <dave@sr71.net>,
	Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] Page Table Isolation (PTI) v4.14 backporting base tree
Date: Sun, 17 Dec 2017 16:16:04 +0100	[thread overview]
Message-ID: <20171217151604.yapemeyswu3vuov4@gmail.com> (raw)

Linus,

Please pull the latest WIP.x86-pti.base-for-linus git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86-pti.base-for-linus

   # HEAD: 2aeb07365bcd489620f71390a7d2031cd4dfb83e x86/mm/kasan: Don't use vmemmap_populate() to initialize shadow

Note, this tree should be pulled after:

  [RFC GIT PULL] Page Table Isolation (PTI) preparatory tree

This tree contains the v4.14 PTI backport preparatory tree, which consists of four 
merges of upstream trees and 7 cherry-picked commits, which the upcoming PTI work 
depends on:

 e5d77a73f364: Merge commit 'upstream-x86-virt' into WIP.x86/mm
 2ec077c186a0: Merge branch 'upstream-acpi-fixes' into WIP.x86/pti.base
 650400b2ccb8: Merge branch 'upstream-x86-selftests' into WIP.x86/pti.base
 0fd2e9c53d82: Merge commit 'upstream-x86-entry' into WIP.x86/mm

 2aeb07365bcd: x86/mm/kasan: Don't use vmemmap_populate() to initialize shadow
 3382290ed2d5: locking/barriers: Convert users of lockless_dereference() to READ_ONCE()
 c2bc66082e10: locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()
 ab95477e7cb3: bpf: fix build issues on um due to mising bpf_perf_event.h
 2fe1bc1f501d: perf/x86: Enable free running PEBS for REGS_USER/INTR
 f2dbad36c55e: x86: Make X86_BUG_FXSAVE_LEAK detectable in CPUID on AMD
 a8b4db562e72: x86/cpufeature: Add User-Mode Instruction Prevention definitions

pulling this should generate a trivial conflict in arch/x86/kernel/cpu/Makefile, 
which after resolution should result in a no-op merge.

 Thanks,

	Ingo

------------------>
Andi Kleen (1):
      perf/x86: Enable free running PEBS for REGS_USER/INTR

Andrey Ryabinin (1):
      x86/mm/kasan: Don't use vmemmap_populate() to initialize shadow

Daniel Borkmann (1):
      bpf: fix build issues on um due to mising bpf_perf_event.h

Ingo Molnar (4):
      Merge commit 'upstream-x86-entry' into WIP.x86/mm
      Merge branch 'upstream-x86-selftests' into WIP.x86/pti.base
      Merge branch 'upstream-acpi-fixes' into WIP.x86/pti.base
      Merge commit 'upstream-x86-virt' into WIP.x86/mm

Ricardo Neri (1):
      x86/cpufeature: Add User-Mode Instruction Prevention definitions

Rudolf Marek (1):
      x86: Make X86_BUG_FXSAVE_LEAK detectable in CPUID on AMD

Will Deacon (2):
      locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()
      locking/barriers: Convert users of lockless_dereference() to READ_ONCE()

[ no-op tree, no diffstat. ]

next             reply	other threads:[~2017-12-17 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17 15:16 Ingo Molnar [this message]
2017-12-17 22:05 ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171217151604.yapemeyswu3vuov4@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dave@sr71.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Be sure your reply has a Subject: header at the top and a blank line before the message body.

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®