diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-10-04 10:25:22 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-10-04 10:25:22 -0700 |
| commit | 7c738cb4ca678e70c4583ab35587f30bfae823e5 (patch) | |
| tree | 38b76c0526f586ce22f2758ccb22bce374367943 /tools/docs/lib | |
| parent | be786eba12c87dc04ad8eac408dc17369c04ad47 (diff) | |
| parent | 3da01ffe1aeaa0d427ab5235ba735226670a80d9 (diff) | |
Merge tag 'x86_entry_for_6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 entry updates from Dave Hansen:
"A pair of x86/entry updates.
The FRED one adjusts the kernel to the latest spec. The spec change
prevents attackers from abusing kernel entry points.
The second one came about because of the LASS work[1]. It moves the
vsyscall emulation code away from depending on X86_PF_INSTR which is
not available on some CPUs. Those CPUs are pretty obscure these days,
but this still seems like the right thing to do. It also makes this
code consistent with some things that the LASS code is going to do.
- Use RIP instead of X86_PF_INSTR for vsyscall emulation
- Remove ENDBR64 from FRED entry points"
Link: https://lore.kernel.org/lkml/20250620135325.3300848-1-kirill.shutemov@linux.intel.com/ [1]
* tag 'x86_entry_for_6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/fred: Remove ENDBR64 from FRED entry points
x86/vsyscall: Do not require X86_PF_INSTR to emulate vsyscall
Diffstat (limited to 'tools/docs/lib')
0 files changed, 0 insertions, 0 deletions