summaryrefslogtreecommitdiff
path: root/samples/ftrace
diff options
context:
space:
mode:
authorPeter Zijlstra <peterz@infradead.org>2022-01-11 12:11:14 +0100
committerBorislav Petkov <bp@suse.de>2022-01-12 16:38:25 +0100
commit9cdbeec4096804083944d05da96bbaf59a1eb4f9 (patch)
tree0a5f6577e801dcb928838528091f1b28d0e86b91 /samples/ftrace
parent82a8954acd93ae95d6252fb93a3d210c8f71b093 (diff)
x86/entry_32: Fix segment exceptions
The LKP robot reported that commit in Fixes: caused a failure. Turns out the ldt_gdt_32 selftest turns into an infinite loop trying to clear the segment. As discovered by Sean, what happens is that PARANOID_EXIT_TO_KERNEL_MODE in the handle_exception_return path overwrites the entry stack data with the task stack data, restoring the "bad" segment value. Instead of having the exception retry the instruction, have it emulate the full instruction. Replace EX_TYPE_POP_ZERO with EX_TYPE_POP_REG which will do the equivalent of: POP %reg; MOV $imm, %reg. In order to encode the segment registers, add them as registers 8-11 for 32-bit. By setting regs->[defg]s the (nested) RESTORE_REGS will pop this value at the end of the exception handler and by increasing regs->sp, it will have skipped the stack slot. This was debugged by Sean Christopherson <seanjc@google.com>. [ bp: Add EX_REG_GS too. ] Fixes: aa93e2ad7464 ("x86/entry_32: Remove .fixup usage") Reported-by: kernel test robot <oliver.sang@intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Signed-off-by: Borislav Petkov <bp@suse.de> Link: https://lore.kernel.org/r/Yd1l0gInc4zRcnt/@hirez.programming.kicks-ass.net
Diffstat (limited to 'samples/ftrace')
0 files changed, 0 insertions, 0 deletions