aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/linux/kcore.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2018-08-26 10:13:21 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2018-08-26 10:13:21 -0700
commit2a8a2b7c49d6eb5f3348892c4676267376cfd40b (patch)
tree2342006a8a8fa0d02b147c4d4482146a9f6353f6 /include/linux/kcore.h
parentMerge branch 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (diff)
parentx86/speculation/l1tf: Suggest what to do on systems with too much RAM (diff)
downloadwireguard-linux-2a8a2b7c49d6eb5f3348892c4676267376cfd40b.tar.xz
wireguard-linux-2a8a2b7c49d6eb5f3348892c4676267376cfd40b.zip
Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 fixes from Thomas Gleixner: - Correct the L1TF fallout on 32bit and the off by one in the 'too much RAM for protection' calculation. - Add a helpful kernel message for the 'too much RAM' case - Unbreak the VDSO in case that the compiler desides to use indirect jumps/calls and emits retpolines which cannot be resolved because the kernel uses its own thunks, which does not work for the VDSO. Make it use the builtin thunks. - Re-export start_thread() which was unexported when the 32/64bit implementation was unified. start_thread() is required by modular binfmt handlers. - Trivial cleanups * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/speculation/l1tf: Suggest what to do on systems with too much RAM x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM x86/kvm/vmx: Remove duplicate l1d flush definitions x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit x86/process: Re-export start_thread() x86/mce: Add notifier_block forward declaration x86/vdso: Fix vDSO build if a retpoline is emitted
Diffstat (limited to 'include/linux/kcore.h')
0 files changed, 0 insertions, 0 deletions