x86: Various cleanups and fixes
Subsystems (3)
Peter Zijlstra
maintainercover x86: Various cleanups and fixes
Hi,
Some few (mostly entry) cleanups.
Please consider.
Peter Zijlstra
maintainerPATCH 1/6 x86/mm: Simplify RESERVE_BRK()
From: Josh Poimboeuf <[email protected]>
RESERVE_BRK() reserves data in the .brk_reservation section. The data is initialized to zero, like BSS, so the macro specifies 'nobits' to prevent the data from taking up space in the vmlinux binary. The only way to get the compiler to do that (without putting the variable in .bss proper) is to use inline asm.
The macro also has a hack which encloses the inline asm in a discarded function, which allows the size to be passed (global inline asm doesn't allow inputs).
Remove the need for the discarded function hack by just stringifying the size rather than supplying it as an input to the inline asm.
--- arch/x86/include/asm/setup.h | 30 +++++++++++------------------- 1 file changed, 11 insertions(+), 19 deletions(-)
arch/x86/include/asm/setup.h +11 -19
@@ -109,27 +109,19 @@ extern unsigned long _brk_end;void *extend_brk (size_t size,size_t align);/* -* Reserve space in the brk section. The name must be unique within -* the file, and somewhat descriptive. The size is in bytes. Must be -* used at file scope. +* Reserve space in the brk section. The name must be unique within the file, +* and somewhat descriptive. The size is in bytes. * -* (This uses a temp function to wrap the asm so we can pass it the -* size parameter; otherwise we wouldn't be able to. We can't use a -* "section" attribute on a normal variable because it always ends up -* being @progbits, which ends up allocating space in the vmlinux -* executable.) +* The allocation is done using inline asm (rather than using a section +* attribute on a normal variable) in order to allow the use of @nobits, so +* that it doesn't take up any space in the vmlinux file. */ -#define RESERVE_BRK (name,sz) \ - static void __section(".discard.text") __noendbr __used notrace \ - __brk_reservation_fn_##name##__(void) { \ - asm volatile ( \ - ".pushsection .brk_reservation,\"aw\",@nobits;" \ - ".brk." #name ":" \ - " 1:.skip %c0;" \ - " .size .brk." #name ", . - 1b;" \ - " .popsection" \ - : : "i" (sz)); \ - } +#define RESERVE_BRK (name, size) \ + asm(".pushsection .brk_reservation,\"aw\",@nobits\n\t" \ + ".brk." #name ":\n\t" \ + ".skip " __stringify(size) "\n\t" \ + ".size .brk." #name ", " __stringify(size) "\n\t" \ + ".popsection\n\t")extern void probe_roms (void );#ifdef __i386__
[tip: x86/asm] x86/mm: Simplify RESERVE_BRK()
The following commit has been merged into the x86/asm branch of tip:
The following commit has been merged into the x86/asm branch of tip:
Commit-ID: a1e2c031ec3949b8c039b739c0b5bf9c30007b00 Gitweb: https://git.kernel.org/tip/a1e2c031ec3949b8c039b739c0b5bf9c30007b00 Author: Josh Poimboeuf <[email protected]> AuthorDate: Fri, 06 May 2022 14:14:32 +02:00 Committer: Borislav Petkov <[email protected]> CommitterDate: Fri, 06 May 2022 15:26:33 +02:00
x86/mm: Simplify RESERVE_BRK()
RESERVE_BRK() reserves data in the .brk_reservation section. The data is initialized to zero, like BSS, so the macro specifies 'nobits' to prevent the data from taking up space in the vmlinux binary. The only way to get the compiler to do that (without putting the variable in .bss proper) is to use inline asm.
The macro also has a hack which encloses the inline asm in a discarded function, which allows the size to be passed (global inline asm doesn't allow inputs).
Remove the need for the discarded function hack by just stringifying the size rather than supplying it as an input to the inline asm.
--- arch/x86/include/asm/setup.h | 30 +++++++++++------------------- 1 file changed, 11 insertions(+), 19 deletions(-)
arch/x86/include/asm/setup.h +11 -19
@@ -109,27 +109,19 @@ extern unsigned long _brk_end;void *extend_brk (size_t size,size_t align);/* -* Reserve space in the brk section. The name must be unique within -* the file, and somewhat descriptive. The size is in bytes. Must be -* used at file scope. +* Reserve space in the brk section. The name must be unique within the file, +* and somewhat descriptive. The size is in bytes. * -* (This uses a temp function to wrap the asm so we can pass it the -* size parameter; otherwise we wouldn't be able to. We can't use a -* "section" attribute on a normal variable because it always ends up -* being @progbits, which ends up allocating space in the vmlinux -* executable.) +* The allocation is done using inline asm (rather than using a section +* attribute on a normal variable) in order to allow the use of @nobits, so +* that it doesn't take up any space in the vmlinux file. */ -#define RESERVE_BRK (name,sz) \ - static void __section(".discard.text") __noendbr __used notrace \ - __brk_reservation_fn_##name##__(void) { \ - asm volatile ( \ - ".pushsection .brk_reservation,\"aw\",@nobits;" \ - ".brk." #name ":" \ - " 1:.skip %c0;" \ - " .size .brk." #name ", . - 1b;" \ - " .popsection" \ - : : "i" (sz)); \ - } +#define RESERVE_BRK (name, size) \ + asm(".pushsection .brk_reservation,\"aw\",@nobits\n\t" \ + ".brk." #name ":\n\t" \ + ".skip " __stringify(size) "\n\t" \ + ".size .brk." #name ", " __stringify(size) "\n\t" \ + ".popsection\n\t")extern void probe_roms (void );#ifdef __i386__
Peter Zijlstra
maintainerPATCH 2/6 x86/entry: Simplify entry_INT80_compat()
In reply to Peter ZijlstraFrom: Linus Torvalds <[email protected]>
Instead of playing silly games with rdi, use rax for simpler and more consistent code.
--- arch/x86/entry/entry_64_compat.S | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-)
arch/x86/entry/entry_64_compat.S +9 -10
@@ -362,26 +362,25 @@ SYM_CODE_START(entry_INT80_compat) /* switch to thread stack expects orig_ax and rdi to be pushed */ pushq %rax /* pt_regs->orig_ax */ - pushq %rdi /* pt_regs->di */ /* Need to switch before accessing the thread stack. */ - SWITCH_TO_KERNEL_CR3 scratch_reg=%rdi + SWITCH_TO_KERNEL_CR3 scratch_reg=%rax /* In the Xen PV case we already run on the thread stack. */ ALTERNATIVE "", "jmp .Lint80_keep_stack", X86_FEATURE_XENPV - movq %rsp, %rdi + movq %rsp, %rax movq PER_CPU_VAR(cpu_current_top_of_stack), %rsp - pushq 6*8(%rdi) /* regs->ss */ - pushq 5*8(%rdi) /* regs->rsp */ - pushq 4*8(%rdi) /* regs->eflags */ - pushq 3*8(%rdi) /* regs->cs */ - pushq 2*8(%rdi) /* regs->ip */ - pushq 1*8(%rdi) /* regs->orig_ax */ - pushq (%rdi) /* pt_regs->di */ + pushq 5*8(%rax) /* regs->ss */ + pushq 4*8(%rax) /* regs->rsp */ + pushq 3*8(%rax) /* regs->eflags */ + pushq 2*8(%rax) /* regs->cs */ + pushq 1*8(%rax) /* regs->ip */ + pushq 0*8(%rax) /* regs->orig_ax */ .Lint80_keep_stack: + pushq %rdi /* pt_regs->di */ pushq %rsi /* pt_regs->si */ xorl %esi, %esi /* nospec si */ pushq %rdx /* pt_regs->dx */
[tip: x86/asm] x86/entry: Simplify entry_INT80_compat()
The following commit has been merged into the x86/asm branch of tip:
The following commit has been merged into the x86/asm branch of tip:
Commit-ID: d205222eb6a8e5e70c21200beb81c6e19ec211d6 Gitweb: https://git.kernel.org/tip/d205222eb6a8e5e70c21200beb81c6e19ec211d6 Author: Linus Torvalds <[email protected]> AuthorDate: Fri, 06 May 2022 14:14:33 +02:00 Committer: Borislav Petkov <[email protected]> CommitterDate: Fri, 06 May 2022 15:49:51 +02:00
x86/entry: Simplify entry_INT80_compat()
Instead of playing silly games with rdi, use rax for simpler and more consistent code.
--- arch/x86/entry/entry_64_compat.S | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-)
arch/x86/entry/entry_64_compat.S +9 -10
@@ -362,26 +362,25 @@ SYM_CODE_START(entry_INT80_compat) /* switch to thread stack expects orig_ax and rdi to be pushed */ pushq %rax /* pt_regs->orig_ax */ - pushq %rdi /* pt_regs->di */ /* Need to switch before accessing the thread stack. */ - SWITCH_TO_KERNEL_CR3 scratch_reg=%rdi + SWITCH_TO_KERNEL_CR3 scratch_reg=%rax /* In the Xen PV case we already run on the thread stack. */ ALTERNATIVE "", "jmp .Lint80_keep_stack", X86_FEATURE_XENPV - movq %rsp, %rdi + movq %rsp, %rax movq PER_CPU_VAR(cpu_current_top_of_stack), %rsp - pushq 6*8(%rdi) /* regs->ss */ - pushq 5*8(%rdi) /* regs->rsp */ - pushq 4*8(%rdi) /* regs->eflags */ - pushq 3*8(%rdi) /* regs->cs */ - pushq 2*8(%rdi) /* regs->ip */ - pushq 1*8(%rdi) /* regs->orig_ax */ - pushq (%rdi) /* pt_regs->di */ + pushq 5*8(%rax) /* regs->ss */ + pushq 4*8(%rax) /* regs->rsp */ + pushq 3*8(%rax) /* regs->eflags */ + pushq 2*8(%rax) /* regs->cs */ + pushq 1*8(%rax) /* regs->ip */ + pushq 0*8(%rax) /* regs->orig_ax */ .Lint80_keep_stack: + pushq %rdi /* pt_regs->di */ pushq %rsi /* pt_regs->si */ xorl %esi, %esi /* nospec si */ pushq %rdx /* pt_regs->dx */
Peter Zijlstra
maintainerPATCH 3/6 x86/entry: Use PUSH_AND_CLEAR_REGS for compat
In reply to Peter ZijlstraSince the upper regs don't exist for ia32 code, preserving them doesn't hurt and it simplifies the code.
This doesn't add any attack surface that would not already be available through INT80.
Notably:
- 32bit SYSENTER: didn't clear si, dx, cx.
- 32bit SYSCALL, INT80: *do* clear si since the C functions don't take a second argument.
- 64bit: didn't clear si since the C functions take a second argument; except the error_entry path might have only one argument, so clearing si was missing here.
32b SYSENTER should be clearing all those 3 registers, nothing uses them and selftests pass.
Unconditionally clear rsi since it simplifies code.
--- arch/x86/entry/calling.h | 1 arch/x86/entry/entry_64_compat.S | 87 +-------------------------------------- 2 files changed, 4 insertions(+), 84 deletions(-)
arch/x86/entry/calling.h +1 -0
@@ -99,6 +99,7 @@ For 32-bit we have the following convent* well before they could be put to use in a speculative execution * gadget. */ + xorl %esi, %esi /* nospec si */ xorl %edx, %edx /* nospec dx */ xorl %ecx, %ecx /* nospec cx */ xorl %r8d, %r8d /* nospec r8 */
arch/x86/entry/entry_64_compat.S +3 -84
105 lines not on this page · raw message
[tip: x86/asm] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
The following commit has been merged into the x86/asm branch of tip:
The following commit has been merged into the x86/asm branch of tip:
Commit-ID: 8c42819b61b8340cff0643e65b5ce6a4144ab155 Gitweb: https://git.kernel.org/tip/8c42819b61b8340cff0643e65b5ce6a4144ab155 Author: Peter Zijlstra <[email protected]> AuthorDate: Fri, 06 May 2022 14:14:34 +02:00 Committer: Borislav Petkov <[email protected]> CommitterDate: Fri, 06 May 2022 15:57:02 +02:00
x86/entry: Use PUSH_AND_CLEAR_REGS for compat
Since the upper regs don't exist for ia32 code, preserving them doesn't hurt and it simplifies the code.
This doesn't add any attack surface that would not already be available through INT80.
Notably:
- 32bit SYSENTER: didn't clear si, dx, cx.
- 32bit SYSCALL, INT80: *do* clear si since the C functions don't take a second argument.
- 64bit: didn't clear si since the C functions take a second argument; except the error_entry path might have only one argument, so clearing si was missing here.
32b SYSENTER should be clearing all those 3 registers, nothing uses them and selftests pass.
Unconditionally clear rsi since it simplifies code.
--- arch/x86/entry/calling.h | 1 +- arch/x86/entry/entry_64_compat.S | 87 +------------------------------ 2 files changed, 4 insertions(+), 84 deletions(-)
arch/x86/entry/calling.h +1 -0
@@ -99,6 +99,7 @@ For 32-bit we have the following conventions - kernel is built with* well before they could be put to use in a speculative execution * gadget. */ + xorl %esi, %esi /* nospec si */ xorl %edx, %edx /* nospec dx */ xorl %ecx, %ecx /* nospec cx */ xorl %r8d, %r8d /* nospec r8 */
arch/x86/entry/entry_64_compat.S +3 -84
105 lines not on this page · raw message
Re: [PATCH 3/6] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
In reply to Peter ZijlstraQuoted 18 lines · Peter Zijlstra
Since the upper regs don't exist for ia32 code, preserving them doesn't hurt and it simplifies the code.
This doesn't add any attack surface that would not already be available through INT80.
Notably:
- 32bit SYSENTER: didn't clear si, dx, cx.
- 32bit SYSCALL, INT80: *do* clear si since the C functions don't take a second argument.
- 64bit: didn't clear si since the C functions take a second argument; except the
error_entrypath might have only one argument, so clearing si was missing here.
Quoted 7 lines
32b SYSENTER should be clearing all those 3 registers, nothing uses them and selftests pass.
Unconditionally clear rsi since it simplifies code.
Signed-off-by Peter Zijlstra (Intel) <[email protected]>Reviewed-by Borislav Petkov <[email protected]>
Re: [PATCH 3/6] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
In reply to Peter ZijlstraQuoted 17 lines · Peter Zijlstra
Since the upper regs don't exist for ia32 code, preserving them doesn't hurt and it simplifies the code.
This doesn't add any attack surface that would not already be available through INT80.
Notably:
- 32bit SYSENTER: didn't clear si, dx, cx.
- 32bit SYSCALL, INT80: *do* clear si since the C functions don't take a second argument.
- 64bit: didn't clear si since the C functions take a second argument; except the
error_entrypath might have only one argument, so clearing si was missing here.
Quoted 7 lines
32b SYSENTER should be clearing all those 3 registers, nothing uses them and selftests pass.
Unconditionally clear rsi since it simplifies code.
Signed-off-by Peter Zijlstra (Intel) <[email protected]>Reviewed-by Borislav Petkov <[email protected]>
linux-next (next-20220519) crashes due to this patch when booting q35:EPYC-Rome in qemu.
[ 20.716975] Run /sbin/init as init process [ 20.790596] init[1]: segfault at f7fd5ca0 ip 00000000f7f5bbc7 sp 00000000ffa06aa0 error 7 in libc.so[f7f51000+4e000] [ 20.793487] Code: 8a 44 24 10 88 41 ff 8b 44 24 10 83 c4 2c 5b 5e 5f 5d c3 53 83 ec 08 8b 5c 24 10 81 fb 00 f0 ff ff 76 0c e8 ba dc ff ff f7 db <89> 18 83 cb ff 83 c4 08 89 d8 5b c3 e8 81 60 ff ff 05 28 84 07 00 [ 20.796332] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 20.796621] CPU: 1 PID: 1 Comm: init Tainted: G W 5.18.0-rc7-next-20220519 #1 [ 20.796724] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 [ 20.796724] Call Trace: [ 20.796724] <TASK> [ 20.796724] dump_stack_lvl+0x57/0x7d [ 20.796724] panic+0x10f/0x28d [ 20.796724] do_exit.cold+0x18/0x48 [ 20.796724] do_group_exit+0x2e/0xb0 [ 20.796724] get_signal+0xb6d/0xb80 [ 20.796724] arch_do_signal_or_restart+0x31/0x760 [ 20.796724] ? show_opcodes.cold+0x1c/0x21 [ 20.796724] ? force_sig_fault+0x49/0x70 [ 20.796724] exit_to_user_mode_prepare+0x131/0x1a0 [ 20.796724] irqentry_exit_to_user_mode+0x5/0x30 [ 20.796724] asm_exc_page_fault+0x27/0x30 [ 20.796724] RIP: 0023:0xf7f5bbc7 [ 20.796724] Code: 8a 44 24 10 88 41 ff 8b 44 24 10 83 c4 2c 5b 5e 5f 5d c3 53 83 ec 08 8b 5c 24 10 81 fb 00 f0 ff ff 76 0c e8 ba dc ff ff f7 db <89> 18 83 cb ff 83 c4 08 89 d8 5b c3 e8 81 60 ff ff 05 28 84 07 00 [ 20.796724] RSP: 002b:00000000ffa06aa0 EFLAGS: 00000217 [ 20.796724] RAX: 00000000f7fd5ca0 RBX: 000000000000000c RCX: 0000000000001000 [ 20.796724] RDX: 0000000000000001 RSI: 00000000f7fd5b60 RDI: 00000000f7fd5b60 [ 20.796724] RBP: 00000000f7fd1c1c R08: 0000000000000000 R09: 0000000000000000 [ 20.796724] R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000 [ 20.796724] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 20.796724] </TASK> [ 20.796724] Kernel Offset: 0x33000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
Bisect log attached. Reverting the patch fixes the problem.
Guenter
---
# bad: [21498d01d045c5b95b93e0a0625ae965b4330ebe] Add linux-next specific files for 20220519
# good: [42226c989789d8da4af1de0c31070c96726d990c] Linux 5.18-rc7
git bisect start 'HEAD' 'v5.18-rc7'
# good: [00ad3ec718d0a85b8fe6b317f07e585650e05073] Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
git bisect good 00ad3ec718d0a85b8fe6b317f07e585650e05073
# bad: [7bbdec75300e073a8fa14d19409af4b43bbaff17] Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
git bisect bad 7bbdec75300e073a8fa14d19409af4b43bbaff17
# good: [c298441f72cd14bbe74ac49a5c60ecf302cc2f97] Merge branch 'drm-next' of https://gitlab.freedesktop.org/agd5f/linux
git bisect good c298441f72cd14bbe74ac49a5c60ecf302cc2f97
# good: [e261ae308e94dc89db3f473db29662942a4dd532] Merge branch 'for-next' of git://git.kernel.dk/linux-block.git
git bisect good e261ae308e94dc89db3f473db29662942a4dd532
# good: [ba821c4223c38f4ec1cc2c7151c8abd4c70e3178] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
git bisect good ba821c4223c38f4ec1cc2c7151c8abd4c70e3178
# good: [2b0b069fc23047b66e1bf6ffd60e7ea5d4e2f484] Merge branch into tip/master: 'smp/core'
git bisect good 2b0b069fc23047b66e1bf6ffd60e7ea5d4e2f484
# bad: [7e2492890410e54a44b5cea9d34ecca45bf74890] Merge branch into tip/master: 'locking/core'
git bisect bad 7e2492890410e54a44b5cea9d34ecca45bf74890
# bad: [9e20f60bad4afb3e1f368e9a61d9813210ce6a29] Merge branch into tip/master: 'x86/cleanups'
git bisect bad 9e20f60bad4afb3e1f368e9a61d9813210ce6a29
# bad: [ab07ef45e638d9fdffbdd2f50521f73096acf2f1] Merge branch into tip/master: 'x86/asm'
git bisect bad ab07ef45e638d9fdffbdd2f50521f73096acf2f1
# good: [81893ca70cddbbce7cde243e0c70de6917b82956] Merge branch into tip/master: 'timers/core'
git bisect good 81893ca70cddbbce7cde243e0c70de6917b82956
# good: [d205222eb6a8e5e70c21200beb81c6e19ec211d6] x86/entry: Simplify entry_INT80_compat()
git bisect good d205222eb6a8e5e70c21200beb81c6e19ec211d6
# bad: [e2ef115813c34ea5380ac5b4879f515070150210] objtool: Fix STACK_FRAME_NON_STANDARD reloc type
git bisect bad e2ef115813c34ea5380ac5b4879f515070150210
# bad: [1b331eeea7b8676fc5dbdf80d0a07e41be226177] x86/entry: Remove skip_r11rcx
git bisect bad 1b331eeea7b8676fc5dbdf80d0a07e41be226177
# bad: [8c42819b61b8340cff0643e65b5ce6a4144ab155] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
git bisect bad 8c42819b61b8340cff0643e65b5ce6a4144ab155
# first bad commit: [8c42819b61b8340cff0643e65b5ce6a4144ab155] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
Peter Zijlstra
maintainerRe: [PATCH 3/6] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
Quoted 21 lines · Guenter Roeck
Quoted 20 lines · Peter Zijlstra
Since the upper regs don't exist for ia32 code, preserving them doesn't hurt and it simplifies the code.
This doesn't add any attack surface that would not already be available through INT80.
Notably:
- 32bit SYSENTER: didn't clear si, dx, cx.
- 32bit SYSCALL, INT80: *do* clear si since the C functions don't take a second argument.
- 64bit: didn't clear si since the C functions take a second argument; except the
error_entrypath might have only one argument, so clearing si was missing here.32b SYSENTER should be clearing all those 3 registers, nothing uses them and selftests pass.
Quoted 7 lines
Quoted 4 lines
Unconditionally clear rsi since it simplifies code.
Signed-off-by Peter Zijlstra (Intel) <[email protected]>Reviewed-by Borislav Petkov <[email protected]>linux-next (next-20220519) crashes due to this patch when booting q35:EPYC-Rome in qemu.
Could you try backing out each of the hunks one at a time? They're all more or less independent.
My bet with this being a #PF on an AMD machine, it's either the SI clear or the SYSCALL change.
Josh Poimboeuf
maintainerRe: [PATCH 3/6] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
Quoted 27 lines · Peter Zijlstra
Quoted 26 lines · Guenter Roeck
Quoted 24 lines · Peter Zijlstra
Since the upper regs don't exist for ia32 code, preserving them doesn't hurt and it simplifies the code.
This doesn't add any attack surface that would not already be available through INT80.
Notably:
- 32bit SYSENTER: didn't clear si, dx, cx.
- 32bit SYSCALL, INT80: *do* clear si since the C functions don't take a second argument.
- 64bit: didn't clear si since the C functions take a second argument; except the
error_entrypath might have only one argument, so clearing si was missing here.32b SYSENTER should be clearing all those 3 registers, nothing uses them and selftests pass.
Unconditionally clear rsi since it simplifies code.
Signed-off-by Peter Zijlstra (Intel) <[email protected]>Reviewed-by Borislav Petkov <[email protected]>
Quoted 8 lines
Quoted 2 lines
linux-next (next-20220519) crashes due to this patch when booting q35:EPYC-Rome in qemu.
Could you try backing out each of the hunks one at a time? They're all more or less independent.
My bet with this being a #PF on an AMD machine, it's either the SI clear or the SYSCALL change.
I think this should fix it:
arch/x86/entry/calling.h +4 -4
@@ -63,7 +63,7 @@ For 32-bit we have the following conventions - kernel is built with* for assembly code: */ -.macro PUSH_REGS rdx=%rdx rax=%rax save_ret=0 +.macro PUSH_REGS rdx=%rdx rcx=%rcx rax=%rax save_ret=0 .if \save_ret pushq %rsi /* pt_regs->si */ movq 8(%rsp), %rsi /* temporarily store the return address in %rsi */
@@ -73,7 +73,7 @@ For 32-bit we have the following conventions - kernel is built with pushq %rsi/* pt_regs->si */ .endif pushq \rdx /* pt_regs->dx */ - pushq %rcx /* pt_regs->cx */ + pushq \rcx /* pt_regs->cx */ pushq \rax /* pt_regs->ax */ pushq %r8 /* pt_regs->r8 */ pushq %r9/* pt_regs->r9 */
@@ -115,8 +115,8 @@ For 32-bit we have the following conventions - kernel is built with .endm -.macro PUSH_AND_CLEAR_REGS rdx=%rdx rax=%rax save_ret=0 - PUSH_REGS rdx=\rdx, rax=\rax, save_ret=\save_ret +.macro PUSH_AND_CLEAR_REGS rdx=%rdx rcx=%rcx rax=%rax save_ret=0 + PUSH_REGS rdx=\rdx, rcx=\rcx, rax=\rax, save_ret=\save_retCLEAR_REGS .endm
arch/x86/entry/entry_64_compat.S +1 -1
@@ -200,7 +200,7 @@ SYM_INNER_LABEL(entry_SYSCALL_compat_safe_stack, SYM_L_GLOBAL) SYM_INNER_LABEL(entry_SYSCALL_compat_after_hwframe, SYM_L_GLOBAL) movl %eax, %eax /* discard orig_ax high bits */ pushq %rax /* pt_regs->orig_ax */ - PUSH_AND_CLEAR_REGS rax=$-ENOSYS + PUSH_AND_CLEAR_REGS rax=$-ENOSYS rcx=%rbx UNWIND_HINT_REGS movq %rsp, %rdi
Josh Poimboeuf
maintainerRe: [PATCH 3/6] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
Quoted 31 lines · Josh Poimboeuf
Quoted 30 lines · Peter Zijlstra
Quoted 28 lines · Guenter Roeck
Quoted 17 lines · Peter Zijlstra
Since the upper regs don't exist for ia32 code, preserving them doesn't hurt and it simplifies the code.
This doesn't add any attack surface that would not already be available through INT80.
Notably:
- 32bit SYSENTER: didn't clear si, dx, cx.
- 32bit SYSCALL, INT80: *do* clear si since the C functions don't take a second argument.
- 64bit: didn't clear si since the C functions take a second argument; except the
error_entrypath might have only one argument, so clearing si was missing here.Quoted 7 lines
32b SYSENTER should be clearing all those 3 registers, nothing uses them and selftests pass.
Unconditionally clear rsi since it simplifies code.
Signed-off-by Peter Zijlstra (Intel) <[email protected]>Reviewed-by Borislav Petkov <[email protected]>linux-next (next-20220519) crashes due to this patch when booting q35:EPYC-Rome in qemu.
Quoted 7 lines
Quoted 5 lines
Could you try backing out each of the hunks one at a time? They're all more or less independent.
My bet with this being a #PF on an AMD machine, it's either the SI clear or the SYSCALL change.
I think this should fix it:
Actually that one had a horrendous bug :-)
Guenter, can you try this one?
From: Josh Poimboeuf <[email protected]>
Subject: [PATCH] x86/entry: Fix register corruption in compat syscall
A panic was reported in the init process on AMD:
Run /sbin/init as init process
init[1]: segfault at f7fd5ca0 ip 00000000f7f5bbc7 sp 00000000ffa06aa0 error 7 in libc.so[f7f51000+4e000]
Code: 8a 44 24 10 88 41 ff 8b 44 24 10 83 c4 2c 5b 5e 5f 5d c3 53 83 ec 08 8b 5c 24 10 81 fb 00 f0 ff ff 76 0c e8 ba dc ff ff f7 db <89> 18 83 cb ff 83 c4 08 89 d8 5b c3 e8 81 60 ff ff 05 28 84 07 00 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b CPU: 1 PID: 1 Comm: init Tainted: G W 5.18.0-rc7-next-20220519 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x57/0x7d panic+0x10f/0x28d do_exit.cold+0x18/0x48 do_group_exit+0x2e/0xb0 get_signal+0xb6d/0xb80 arch_do_signal_or_restart+0x31/0x760 ? show_opcodes.cold+0x1c/0x21 ? force_sig_fault+0x49/0x70 exit_to_user_mode_prepare+0x131/0x1a0 irqentry_exit_to_user_mode+0x5/0x30 asm_exc_page_fault+0x27/0x30 RIP: 0023:0xf7f5bbc7 Code: 8a 44 24 10 88 41 ff 8b 44 24 10 83 c4 2c 5b 5e 5f 5d c3 53 83 ec 08 8b 5c 24 10 81 fb 00 f0 ff ff 76 0c e8 ba dc ff ff f7 db <89> 18 83 cb ff 83 c4 08 89 d8 5b c3 e8 81 60 ff ff 05 28 84 07 00 RSP: 002b:00000000ffa06aa0 EFLAGS: 00000217 RAX: 00000000f7fd5ca0 RBX: 000000000000000c RCX: 0000000000001000 RDX: 0000000000000001 RSI: 00000000f7fd5b60 RDI: 00000000f7fd5b60 RBP: 00000000f7fd1c1c R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK>
The task's CX register got corrupted by commit 8c42819b61b8 ("x86/entry:
Use PUSH_AND_CLEAR_REGS for compat"), which overlooked the fact that compat SYSCALL had the user's CX value stored in BP.
Before that commit, CX was saved from its stashed value in BP:
pushq %rbp /* pt_regs->cx (stashed in bp) */
But then it got changed to:
pushq %rcx /* pt_regs->cx */
resulting in the wrong value getting saved and later restored back to the user. Fix it by pushing the correct value again (BP) for regs->cx.
--- arch/x86/entry/calling.h | 8 ++++---- arch/x86/entry/entry_64_compat.S | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-)
arch/x86/entry/calling.h +4 -4
@@ -63,7 +63,7 @@ For 32-bit we have the following conventions - kernel is built with* for assembly code: */ -.macro PUSH_REGS rdx=%rdx rax=%rax save_ret=0 +.macro PUSH_REGS rdx=%rdx rcx=%rcx rax=%rax save_ret=0 .if \save_ret pushq %rsi /* pt_regs->si */ movq 8(%rsp), %rsi /* temporarily store the return address in %rsi */
@@ -73,7 +73,7 @@ For 32-bit we have the following conventions - kernel is built with pushq %rsi/* pt_regs->si */ .endif pushq \rdx /* pt_regs->dx */ - pushq %rcx /* pt_regs->cx */ + pushq \rcx /* pt_regs->cx */ pushq \rax /* pt_regs->ax */ pushq %r8 /* pt_regs->r8 */ pushq %r9/* pt_regs->r9 */
@@ -115,8 +115,8 @@ For 32-bit we have the following conventions - kernel is built with .endm -.macro PUSH_AND_CLEAR_REGS rdx=%rdx rax=%rax save_ret=0 - PUSH_REGS rdx=\rdx, rax=\rax, save_ret=\save_ret +.macro PUSH_AND_CLEAR_REGS rdx=%rdx rcx=%rcx rax=%rax save_ret=0 + PUSH_REGS rdx=\rdx, rcx=\rcx, rax=\rax, save_ret=\save_retCLEAR_REGS .endm
arch/x86/entry/entry_64_compat.S +1 -1
@@ -200,7 +200,7 @@ SYM_INNER_LABEL(entry_SYSCALL_compat_safe_stack, SYM_L_GLOBAL) SYM_INNER_LABEL(entry_SYSCALL_compat_after_hwframe, SYM_L_GLOBAL) movl %eax, %eax /* discard orig_ax high bits */ pushq %rax /* pt_regs->orig_ax */ - PUSH_AND_CLEAR_REGS rax=$-ENOSYS + PUSH_AND_CLEAR_REGS rcx=%rbp rax=$-ENOSYS UNWIND_HINT_REGS movq %rsp, %rdi
Signature · 1 line
2.34.3
Re: [PATCH 3/6] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
arch/x86/entry/entry_64_compat.S SYM_INNER_LABEL(entry_SYSCALL_compat_safe_stack, SYM_L_GLOBAL) · line 203
Quoted 11 lines · Josh Poimboeuf
arch/x86/entry/entry_64_compat.S +1
-1@@ -200,7 +200,7 @@ SYM_INNER_LABEL(entry_SYSCALL_compat_safe_stack, SYM_L_GLOBAL) SYM_INNER_LABEL(entry_SYSCALL_compat_after_hwframe, SYM_L_GLOBAL) movl %eax, %eax /* discard orig_ax high bits */ pushq %rax /* pt_regs->orig_ax */ - PUSH_AND_CLEAR_REGS rax=$-ENOSYS + PUSH_AND_CLEAR_REGS rcx=%rbp rax=$-ENOSYS
Some comments need to be here to explain why %rcx is stashed in %rbp.
The code doing the stash in userspace may be in arch/x86/entry/vdso/vdso32/system_call.S (see SYSCALL_SEQUENCE)
Thanks
Lai
Re: [PATCH 3/6] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
Quoted 15 lines · Lai Jiangshan
arch/x86/entry/entry_64_compat.S SYM_INNER_LABEL(entry_SYSCALL_compat_safe_stack, SYM_L_GLOBAL) · line 203
Quoted 11 lines · Josh Poimboeuf
arch/x86/entry/entry_64_compat.S +1
-1@@ -200,7 +200,7 @@ SYM_INNER_LABEL(entry_SYSCALL_compat_safe_stack, SYM_L_GLOBAL) SYM_INNER_LABEL(entry_SYSCALL_compat_after_hwframe, SYM_L_GLOBAL) movl %eax, %eax /* discard orig_ax high bits */ pushq %rax /* pt_regs->orig_ax */ - PUSH_AND_CLEAR_REGS rax=$-ENOSYS + PUSH_AND_CLEAR_REGS rcx=%rbp rax=$-ENOSYSSome comments need to be here to explain why %rcx is stashed in %rbp.
I am curious. That comment wasn't needed before the problem fixed here was introduced. The comment is unrelated to the bug fix. Why is it needed now, and why would it be a prerequisite for fixing a critical bug ? Shouldn't that comment be added in a separate patch ?
Thanks,
Guenter
Josh Poimboeuf
maintainerRe: [PATCH 3/6] x86/entry: Use PUSH_AND_CLEAR_REGS for compat
In reply to Lai JiangshanQuoted 15 lines · Lai Jiangshan
arch/x86/entry/entry_64_compat.S SYM_INNER_LABEL(entry_SYSCALL_compat_safe_stack, SYM_L_GLOBAL) · line 203
Quoted 11 lines · Josh Poimboeuf
arch/x86/entry/entry_64_compat.S +1
-1@@ -200,7 +200,7 @@ SYM_INNER_LABEL(entry_SYSCALL_compat_safe_stack, SYM_L_GLOBAL) SYM_INNER_LABEL(entry_SYSCALL_compat_after_hwframe, SYM_L_GLOBAL) movl %eax, %eax /* discard orig_ax high bits */ pushq %rax /* pt_regs->orig_ax */ - PUSH_AND_CLEAR_REGS rax=$-ENOSYS + PUSH_AND_CLEAR_REGS rcx=%rbp rax=$-ENOSYSSome comments need to be here to explain why %rcx is stashed in %rbp.
Quoted 2 lines
The code doing the stash in userspace may be in
arch/x86/entry/vdso/vdso32/system_call.S(seeSYSCALL_SEQUENCE)
I do agree a comment would be good, but looking at that maze, I'm not sure I'm qualified to give it a proper one ;-)
My best theory is: __kernel_vsyscall() stashes CX in BP before SYSCALL can overwrite it, because SYSCALL uses CX to stash the return address. And then PUSH_AND_CLEAR_REGS puts the original CX value back in pt_regs, because CX is (presumably?) a syscall function argument.
My patch description said that CX must have gotten corrupted in user space, but that's wrong because __kernel_vsyscall() pushes/pops CX around the SYSCALL.
But alas it's too late to fix the commit log because it's already been committed and the tip maintainers are getting pull requests ready for the merge window.
Signature · 1 line
Josh
Peter Zijlstra
maintainerPATCH 4/6 x86/entry: Remove skip_r11rcx
In reply to Peter ZijlstraYes, r11 and rcx have been restored previously, but since we're popping them anyway (into rsi) might as well pop them into their own regs -- setting them to the value they already are.
Less magical code.
--- arch/x86/entry/calling.h | 10 +--------- arch/x86/entry/entry_64.S | 3 +-- 2 files changed, 2 insertions(+), 11 deletions(-)
arch/x86/entry/calling.h +1 -9
@@ -120,27 +120,19 @@ For 32-bit we have the following conventCLEAR_REGS .endm -.macro POP_REGS pop_rdi=1 skip_r11rcx=0 +.macro POP_REGS pop_rdi=1 popq %r15 popq %r14 popq %r13 popq %r12 popq %rbp popq %rbx - .if \skip_r11rcx - popq %rsi - .else popq %r11 - .endif popq %r10 popq %r9 popq %r8 popq %rax - .if \skip_r11rcx - popq %rsi - .else popq %rcx - .endif popq %rdx popq %rsi .if \pop_rdi
arch/x86/entry/entry_64.S +1 -2
@@ -191,8 +191,7 @@ SYM_INNER_LABEL(entry_SYSCALL_64_after_h * perf profiles. Nothing jumps here. */ syscall_return_via_sysret: - /* rcx and r11 are already restored (see code above) */ - POP_REGS pop_rdi=0 skip_r11rcx=1 + POP_REGS pop_rdi=0 /* * Now all regs are restored except RSP and RDI.
[tip: x86/asm] x86/entry: Remove skip_r11rcx
The following commit has been merged into the x86/asm branch of tip:
The following commit has been merged into the x86/asm branch of tip:
Commit-ID: 1b331eeea7b8676fc5dbdf80d0a07e41be226177 Gitweb: https://git.kernel.org/tip/1b331eeea7b8676fc5dbdf80d0a07e41be226177 Author: Peter Zijlstra <[email protected]> AuthorDate: Fri, 06 May 2022 14:14:35 +02:00 Committer: Borislav Petkov <[email protected]> CommitterDate: Fri, 06 May 2022 15:58:19 +02:00
x86/entry: Remove skip_r11rcx
Yes, r11 and rcx have been restored previously, but since they're being popped anyway (into rsi) might as well pop them into their own regs -- setting them to the value they already are.
Less magical code.
--- arch/x86/entry/calling.h | 10 +--------- arch/x86/entry/entry_64.S | 3 +-- 2 files changed, 2 insertions(+), 11 deletions(-)
arch/x86/entry/calling.h +1 -9
@@ -120,27 +120,19 @@ For 32-bit we have the following conventions - kernel is built withCLEAR_REGS .endm -.macro POP_REGS pop_rdi=1 skip_r11rcx=0 +.macro POP_REGS pop_rdi=1 popq %r15 popq %r14 popq %r13 popq %r12 popq %rbp popq %rbx - .if \skip_r11rcx - popq %rsi - .else popq %r11 - .endif popq %r10 popq %r9 popq %r8 popq %rax - .if \skip_r11rcx - popq %rsi - .else popq %rcx - .endif popq %rdx popq %rsi .if \pop_rdi
arch/x86/entry/entry_64.S +1 -2
@@ -191,8 +191,7 @@ SYM_INNER_LABEL(entry_SYSCALL_64_after_hwframe, SYM_L_GLOBAL) * perf profiles. Nothing jumps here. */ syscall_return_via_sysret: - /* rcx and r11 are already restored (see code above) */ - POP_REGS pop_rdi=0 skip_r11rcx=1 + POP_REGS pop_rdi=0 /* * Now all regs are restored except RSP and RDI.
Re: [PATCH 4/6] x86/entry: Remove skip_r11rcx
In reply to Peter ZijlstraQuoted 8 lines · Peter Zijlstra
Yes, r11 and rcx have been restored previously, but since we're popping them anyway (into rsi) might as well pop them into their own regs -- setting them to the value they already are.
Less magical code.
Signed-off-by Peter Zijlstra (Intel) <[email protected]>
Peter Zijlstra
maintainerPATCH 5/6 linkage: Fix issue with missing symbol size
In reply to Peter ZijlstraOccasionally, typically when a function doesn't end with 'ret', an alias on that function will have 0 size.
The difference between what GCC generates and our linkage magic, is that GCC doesn't appear to provide .size for the alias'ed symbol at all. And indeed, removing this directive cures the issue.
Additionally, GCC also doesn't emit .type for alias symbols either, so also omit that.
--- include/linux/linkage.h | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)
include/linux/linkage.h +6 -9
@@ -171,12 +171,9 @@/* SYM_ALIAS -- use only if you have to */ #ifndef SYM_ALIAS -#define SYM_ALIAS (alias, name, sym_type, linkage) \ - linkage(alias) ASM_NL \ - .set alias, name ASM_NL \ - .type alias sym_type ASM_NL \ - .set .L__sym_size_##alias, .L__sym_size_##name ASM_NL \ - .size alias, .L__sym_size_##alias +#define SYM_ALIAS (alias, name, linkage) \ + linkage(alias) ASM_NL \ + .set alias, name ASM_NL#endif /* === code annotations === */
@@ -261,7 +258,7 @@*/ #ifndef SYM_FUNC_ALIAS #define SYM_FUNC_ALIAS (alias, name) \ - SYM_ALIAS(alias, name, SYM_T_FUNC, SYM_L_GLOBAL) + SYM_ALIAS(alias, name, SYM_L_GLOBAL)#endif /*
@@ -269,7 +266,7 @@*/ #ifndef SYM_FUNC_ALIAS_LOCAL #define SYM_FUNC_ALIAS_LOCAL (alias, name) \ - SYM_ALIAS(alias, name, SYM_T_FUNC, SYM_L_LOCAL) + SYM_ALIAS(alias, name, SYM_L_LOCAL)#endif /*
@@ -277,7 +274,7 @@*/ #ifndef SYM_FUNC_ALIAS_WEAK #define SYM_FUNC_ALIAS_WEAK (alias, name) \ - SYM_ALIAS(alias, name, SYM_T_FUNC, SYM_L_WEAK) + SYM_ALIAS(alias, name, SYM_L_WEAK)#endif /* SYM_CODE_START -- use for non-C (special) functions */
[tip: x86/asm] linkage: Fix issue with missing symbol size
The following commit has been merged into the x86/asm branch of tip:
The following commit has been merged into the x86/asm branch of tip:
Commit-ID: 3ff5f7840979aa36d47a6a00694826c78d63bf3c Gitweb: https://git.kernel.org/tip/3ff5f7840979aa36d47a6a00694826c78d63bf3c Author: Peter Zijlstra <[email protected]> AuthorDate: Fri, 06 May 2022 14:14:36 +02:00 Committer: Borislav Petkov <[email protected]> CommitterDate: Fri, 06 May 2022 15:59:39 +02:00
linkage: Fix issue with missing symbol size
Occasionally, typically when a function doesn't end with 'ret', an alias on that function will have 0 size.
The difference between what GCC generates and our linkage magic, is that GCC doesn't appear to provide .size for the alias'ed symbol at all. And indeed, removing this directive cures the issue.
Additionally, GCC also doesn't emit .type for alias symbols either, so also omit that.
--- include/linux/linkage.h | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)
include/linux/linkage.h +6 -9
@@ -171,12 +171,9 @@/* SYM_ALIAS -- use only if you have to */ #ifndef SYM_ALIAS -#define SYM_ALIAS (alias, name, sym_type, linkage) \ - linkage(alias) ASM_NL \ - .set alias, name ASM_NL \ - .type alias sym_type ASM_NL \ - .set .L__sym_size_##alias, .L__sym_size_##name ASM_NL \ - .size alias, .L__sym_size_##alias +#define SYM_ALIAS (alias, name, linkage) \ + linkage(alias) ASM_NL \ + .set alias, name ASM_NL#endif /* === code annotations === */
@@ -261,7 +258,7 @@*/ #ifndef SYM_FUNC_ALIAS #define SYM_FUNC_ALIAS (alias, name) \ - SYM_ALIAS(alias, name, SYM_T_FUNC, SYM_L_GLOBAL) + SYM_ALIAS(alias, name, SYM_L_GLOBAL)#endif /*
@@ -269,7 +266,7 @@*/ #ifndef SYM_FUNC_ALIAS_LOCAL #define SYM_FUNC_ALIAS_LOCAL (alias, name) \ - SYM_ALIAS(alias, name, SYM_T_FUNC, SYM_L_LOCAL) + SYM_ALIAS(alias, name, SYM_L_LOCAL)#endif /*
@@ -277,7 +274,7 @@*/ #ifndef SYM_FUNC_ALIAS_WEAK #define SYM_FUNC_ALIAS_WEAK (alias, name) \ - SYM_ALIAS(alias, name, SYM_T_FUNC, SYM_L_WEAK) + SYM_ALIAS(alias, name, SYM_L_WEAK)#endif /* SYM_CODE_START -- use for non-C (special) functions */
Peter Zijlstra
maintainerPATCH 6/6 objtool: Fix STACK_FRAME_NON_STANDARD reloc type
In reply to Peter ZijlstraSTACK_FRAME_NON_STANDARD results in inconsistent relocation types depending on .c or .S usage:
Relocation section '.rela.discard.func_stack_frame_non_standard' at offset 0x3c01090 contains 5 entries:
Offset Info Type Symbol's Value Symbol's Name + Addend
0000000000000000 00020c2200000002 R_X86_64_PC32 0000000000047b40 do_suspend_lowlevel + 0 0000000000000008 0002461e00000001 R_X86_64_64 00000000000480a0 machine_real_restart + 0 0000000000000010 0000001400000001 R_X86_64_64 0000000000000000 .rodata + b3d4 0000000000000018 0002444600000002 R_X86_64_PC32 00000000000678a0 __efi64_thunk + 0 0000000000000020 0002659d00000001 R_X86_64_64 0000000000113160 __crash_kexec + 0
--- include/linux/objtool.h | 4 +++- tools/include/linux/objtool.h | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-)
include/linux/objtool.h +3 -1
@@ -2,6 +2,8 @@#ifndef _LINUX_OBJTOOL_H#define _LINUX_OBJTOOL_H +#include <asm/asm.h> +#ifndef __ASSEMBLY__#include <linux/types.h>
@@ -137,7 +139,7 @@ struct unwind_hint { .macro STACK_FRAME_NON_STANDARD func:req .pushsection .discard.func_stack_frame_non_standard,"aw" - .long \func - . + _ASM_PTR \func .popsection .endm
tools/include/linux/objtool.h +3 -1
@@ -2,6 +2,8 @@#ifndef _LINUX_OBJTOOL_H#define _LINUX_OBJTOOL_H +#include <asm/asm.h> +#ifndef __ASSEMBLY__#include <linux/types.h>
@@ -137,7 +139,7 @@ struct unwind_hint { .macro STACK_FRAME_NON_STANDARD func:req .pushsection .discard.func_stack_frame_non_standard,"aw" - .long \func - . + _ASM_PTR \func .popsection .endm
[tip: x86/asm] objtool: Fix STACK_FRAME_NON_STANDARD reloc type
The following commit has been merged into the x86/asm branch of tip:
The following commit has been merged into the x86/asm branch of tip:
Commit-ID: 38f3803fb4fa588ef7645048285493efbe264d79 Gitweb: https://git.kernel.org/tip/38f3803fb4fa588ef7645048285493efbe264d79 Author: Peter Zijlstra <[email protected]> AuthorDate: Fri, 06 May 2022 14:14:37 +02:00 Committer: Borislav Petkov <[email protected]> CommitterDate: Fri, 06 May 2022 16:07:06 +02:00
objtool: Fix STACK_FRAME_NON_STANDARD reloc type
STACK_FRAME_NON_STANDARD results in inconsistent relocation types depending on .c or .S usage:
Relocation section '.rela.discard.func_stack_frame_non_standard' at offset 0x3c01090 contains 5 entries:
Offset Info Type Symbol's Value Symbol's Name + Addend
0000000000000000 00020c2200000002 R_X86_64_PC32 0000000000047b40 do_suspend_lowlevel + 0 0000000000000008 0002461e00000001 R_X86_64_64 00000000000480a0 machine_real_restart + 0 0000000000000010 0000001400000001 R_X86_64_64 0000000000000000 .rodata + b3d4 0000000000000018 0002444600000002 R_X86_64_PC32 00000000000678a0 __efi64_thunk + 0 0000000000000020 0002659d00000001 R_X86_64_64 0000000000113160 __crash_kexec + 0
--- include/linux/objtool.h | 4 +++- tools/include/linux/objtool.h | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-)
include/linux/objtool.h +3 -1
@@ -2,6 +2,8 @@#ifndef _LINUX_OBJTOOL_H#define _LINUX_OBJTOOL_H +#include <asm/asm.h> +#ifndef __ASSEMBLY__#include <linux/types.h>
@@ -137,7 +139,7 @@ struct unwind_hint { .macro STACK_FRAME_NON_STANDARD func:req .pushsection .discard.func_stack_frame_non_standard,"aw" - .long \func - . + _ASM_PTR \func .popsection .endm
tools/include/linux/objtool.h +3 -1
@@ -2,6 +2,8 @@#ifndef _LINUX_OBJTOOL_H#define _LINUX_OBJTOOL_H +#include <asm/asm.h> +#ifndef __ASSEMBLY__#include <linux/types.h>
@@ -137,7 +139,7 @@ struct unwind_hint { .macro STACK_FRAME_NON_STANDARD func:req .pushsection .discard.func_stack_frame_non_standard,"aw" - .long \func - . + _ASM_PTR \func .popsection .endm
Re: [PATCH 6/6] objtool: Fix STACK_FRAME_NON_STANDARD reloc type
In reply to Peter ZijlstraQuoted 5 lines · Peter Zijlstra
STACK_FRAME_NON_STANDARDresults in inconsistent relocation types depending on .c or .S usage:Relocation section '.rela.discard.func_stack_frame_non_standard' at offset
0x3c01090contains 5 entries:
Offset Info Type Symbol's Value Symbol's Name + Addend
Quoted 7 lines
0000000000000000 00020c2200000002 R_X86_64_PC32 0000000000047b40 do_suspend_lowlevel + 0 0000000000000008 0002461e00000001 R_X86_64_64 00000000000480a0 machine_real_restart + 0 0000000000000010 0000001400000001 R_X86_64_64 0000000000000000 .rodata + b3d4 0000000000000018 0002444600000002 R_X86_64_PC32 00000000000678a0 __efi64_thunk + 0 0000000000000020 0002659d00000001 R_X86_64_64 0000000000113160 __crash_kexec + 0Signed-off-by Peter Zijlstra (Intel) <[email protected]>
Signature · 1 line
Josh
[tip: x86/asm] objtool: Fix STACK_FRAME_NON_STANDARD reloc type
In reply to Peter ZijlstraThe following commit has been merged into the x86/asm branch of tip:
The following commit has been merged into the x86/asm branch of tip:
Commit-ID: e2ef115813c34ea5380ac5b4879f515070150210 Gitweb: https://git.kernel.org/tip/e2ef115813c34ea5380ac5b4879f515070150210 Author: Peter Zijlstra <[email protected]> AuthorDate: Fri, 06 May 2022 14:14:37 +02:00 Committer: Peter Zijlstra <[email protected]> CommitterDate: Fri, 06 May 2022 22:20:43 +02:00
objtool: Fix STACK_FRAME_NON_STANDARD reloc type
STACK_FRAME_NON_STANDARD results in inconsistent relocation types depending on .c or .S usage:
Relocation section '.rela.discard.func_stack_frame_non_standard' at offset 0x3c01090 contains 5 entries:
Offset Info Type Symbol's Value Symbol's Name + Addend
0000000000000000 00020c2200000002 R_X86_64_PC32 0000000000047b40 do_suspend_lowlevel + 0 0000000000000008 0002461e00000001 R_X86_64_64 00000000000480a0 machine_real_restart + 0 0000000000000010 0000001400000001 R_X86_64_64 0000000000000000 .rodata + b3d4 0000000000000018 0002444600000002 R_X86_64_PC32 00000000000678a0 __efi64_thunk + 0 0000000000000020 0002659d00000001 R_X86_64_64 0000000000113160 __crash_kexec + 0
--- include/linux/objtool.h | 4 +++- tools/include/linux/objtool.h | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-)
include/linux/objtool.h +3 -1
@@ -40,6 +40,8 @@ struct unwind_hint {#ifdef CONFIG_STACK_VALIDATION +#include <asm/asm.h> +#ifndef __ASSEMBLY__#define UNWIND_HINT (sp_reg, sp_offset, type, end) \
@@ -137,7 +139,7 @@ struct unwind_hint { .macro STACK_FRAME_NON_STANDARD func:req .pushsection .discard.func_stack_frame_non_standard,"aw" - .long \func - . + _ASM_PTR \func .popsection .endm
tools/include/linux/objtool.h +3 -1
@@ -40,6 +40,8 @@ struct unwind_hint {#ifdef CONFIG_STACK_VALIDATION +#include <asm/asm.h> +#ifndef __ASSEMBLY__#define UNWIND_HINT (sp_reg, sp_offset, type, end) \
@@ -137,7 +139,7 @@ struct unwind_hint { .macro STACK_FRAME_NON_STANDARD func:req .pushsection .discard.func_stack_frame_non_standard,"aw" - .long \func - . + _ASM_PTR \func .popsection .endm