diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2018-08-26 20:13:21 +0300 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-08-26 20:13:21 +0300 |
| commit | 2a8a2b7c49d6eb5f3348892c4676267376cfd40b (patch) | |
| tree | 2342006a8a8fa0d02b147c4d4482146a9f6353f6 /mm/page_poison.c | |
| parent | de3750351c0de35472299506ace61a01f2bfc567 (diff) | |
| parent | 6a012288d6906fee1dbc244050ade1dafe4a9c8d (diff) | |
| download | linux-2a8a2b7c49d6eb5f3348892c4676267376cfd40b.tar.xz | |
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 'mm/page_poison.c')
0 files changed, 0 insertions, 0 deletions