objtool: Add support for Arm64
Subsystems (4)
v2 cover objtool: Add support for Arm64
As of now, objtool only supports the x86_64 architecture but the groundwork has already been done in order to add support for other architectures without too much effort.
This series of patches adds support for the arm64 architecture based on the Armv8.5 Architecture Reference Manual.
Objtool will be a valuable tool to progress and provide more guarentees on live patching which is a work in progress for arm64.
Once we have the base of objtool working the next steps will be to port Peter Z's uaccess validation for arm64.
RFC: In order to differentiate the different uses of the brk instruction on arm64 I intended to use the include/generated/asm-offsets.h header file (copying it to tools/include/generated/asm-offsets.h). However since in is generated later than objtool in the build process I wasn't able to do it. I wanted to use it to have access to the info about the struct alt_instr and struct bug_entry.
Noteworthy points:
* I still haven't figured out how to detect switch-tables on arm64. I have a better understanding of them but still haven't implemented checks as it doesn't look trivial at all.
* I still use the arch_is_sibling_call function to differentiate the use cases of the br instruction on arm64. Even though I updated the checks, it is still based on going back in the instruction stream, which as Peter Z. pointed out is not safe. I shall work on an alternative solution.
Changes from V2:
* Rebase on the -tip tree (which contains the latest objtool features)
* Split into more precise patches in order to highlight the changes that were made.
* Correct patches coding style to comply with linux's style.
* Refactor some code to avoid generating a fake instruction when decoding load/store of pairs of registers.
* Make more elegant checks for arch-dependent features (switch-tables, special sections)
* Include some patches to add exceptions in the kernel to prevent objtool from checking/warning in particular cases.
* Introduce a new instruction type (INSN_UNKNOWN) to handle the cases when some data is stored inside a section marked as containing executable instructions.
Raphael Gault (16):
objtool: Add abstraction for computation of symbols offsets
objtool: orc: Refactor ORC API for other architectures to implement.
objtool: Move registers and control flow to arch-dependent code
objtool: arm64: Add required implementation for supporting the aarch64
architecture in objtool.
objtool: arm64: Handle hypercalls as nops
arm64: alternative: Mark .altinstr_replacement as containing
executable instructions
objtool: special: Adapt special section handling
objtool: arm64: Adapt the stack frame checks for arm architecture
arm64: assembler: Add macro to annotate asm function having non
standard stack-frame.
arm64: sleep: Prevent stack frame warnings from objtool
objtool: arm64: Enable stack validation for arm64
arm64: kvm: Annotate non-standard stack frame functions
arm64: kernel: Add exception on kuser32 to prevent stack analysis
arm64: crypto: Add exceptions for crypto object to prevent stack
analysis
objtool: Introduce INSN_UNKNOWN type
arm64: kernel: Annotate non-standard stack frame functions
arch/arm64/Kconfig | 1 +
arch/arm64/crypto/Makefile | 3 +
arch/arm64/include/asm/alternative.h | 2 +-
arch/arm64/include/asm/assembler.h | 13 +
arch/arm64/kernel/Makefile | 3 +
arch/arm64/kernel/hyp-stub.S | 2 +
arch/arm64/kernel/sleep.S | 4 +
arch/arm64/kvm/hyp-init.S | 2 +
arch/arm64/kvm/hyp/entry.S | 2 +
tools/objtool/Build | 2 -
tools/objtool/arch.h | 21 +-
tools/objtool/arch/arm64/Build | 8 +
tools/objtool/arch/arm64/bit_operations.c | 67 +
tools/objtool/arch/arm64/decode.c | 2809 +++++++++++++++++
.../objtool/arch/arm64/include/arch_special.h | 42 +
.../arch/arm64/include/asm/orc_types.h | 96 +
.../arch/arm64/include/bit_operations.h | 24 +
tools/objtool/arch/arm64/include/cfi.h | 74 +
.../objtool/arch/arm64/include/insn_decode.h | 211 ++
tools/objtool/arch/arm64/orc_dump.c | 26 +
tools/objtool/arch/arm64/orc_gen.c | 40 +
tools/objtool/arch/x86/Build | 3 +
tools/objtool/arch/x86/decode.c | 16 +
tools/objtool/arch/x86/include/arch_special.h | 45 +
tools/objtool/{ => arch/x86/include}/cfi.h | 0
tools/objtool/{ => arch/x86}/orc_dump.c | 4 +-
tools/objtool/{ => arch/x86}/orc_gen.c | 104 +-
tools/objtool/check.c | 239 +-
tools/objtool/check.h | 1 +
tools/objtool/elf.c | 3 +-
tools/objtool/orc.h | 4 +-
tools/objtool/special.c | 28 +-
tools/objtool/special.h | 3 +
33 files changed, 3753 insertions(+), 149 deletions(-)
create mode 100644 tools/objtool/arch/arm64/Build
create mode 100644 tools/objtool/arch/arm64/bit_operations.c
create mode 100644 tools/objtool/arch/arm64/decode.c
create mode 100644 tools/objtool/arch/arm64/include/arch_special.h
create mode 100644 tools/objtool/arch/arm64/include/asm/orc_types.h
create mode 100644 tools/objtool/arch/arm64/include/bit_operations.h
create mode 100644 tools/objtool/arch/arm64/include/cfi.h
create mode 100644 tools/objtool/arch/arm64/include/insn_decode.h
create mode 100644 tools/objtool/arch/arm64/orc_dump.c
create mode 100644 tools/objtool/arch/arm64/orc_gen.c
create mode 100644 tools/objtool/arch/x86/include/arch_special.h
rename tools/objtool/{ => arch/x86/include}/cfi.h (100%)
rename tools/objtool/{ => arch/x86}/orc_dump.c (98%)
rename tools/objtool/{ => arch/x86}/orc_gen.c (69%)Signature · 1 line
2.17.1
RFC v2 1/16 objtool: Add abstraction for computation of symbols offsets
The jump destination and relocation offset used previously are only reliable on x86_64 architecture. We abstract these computations by calling arch-dependent implementations.
--- tools/objtool/arch.h | 6 ++++++ tools/objtool/arch/x86/decode.c | 11 +++++++++++ tools/objtool/check.c | 15 ++++++++++----- 3 files changed, 27 insertions(+), 5 deletions(-)
tools/objtool/arch.h +6 -0
@@ -76,6 +76,8 @@ struct stack_op {struct op_src src; }; +struct instruction ; +void arch_initial_func_cfi_state (struct cfi_state *state); int arch_decode_instruction(struct elf *elf, struct section *sec,
@@ -85,4 +87,8 @@ int arch_decode_instruction(struct elf *elf, struct section *sec,bool arch_callee_saved_reg (unsigned char reg); +unsigned long arch_jump_destination (struct instruction *insn); + +unsigned long arch_dest_rela_offset (int addend); +#endif /* _ARCH_H */
tools/objtool/arch/x86/decode.c +11 -0
@@ -23,6 +23,7 @@#include "lib/inat.c" #include "lib/insn.c" +#include "../../check.h" #include "../../elf.h" #include "../../arch.h" #include "../../warn.h"
@@ -78,6 +79,11 @@ bool arch_callee_saved_reg(unsigned char reg) } } +unsigned long arch_dest_rela_offset (int addend) +{ +return addend +4 ; +} + int arch_decode_instruction(struct elf *elf, struct section *sec, unsigned long offset, unsigned int maxlen, unsigned int *len, unsigned char *type,
@@ -509,3 +515,8 @@ void arch_initial_func_cfi_state(struct cfi_state *state) state->regs[16 ].base =CFI_CFA ; state->regs[16 ].offset =-8 ; } + +unsigned long arch_jump_destination (struct instruction *insn) +{ +return insn->offset + insn->len + insn->immediate; +}
tools/objtool/check.c +10 -5
@@ -574,7 +574,7 @@ static int add_jump_destinations(struct objtool_file *file) insn->len);if (!rela) { dest_sec = insn->sec; - dest_off = insn->offset + insn->len + insn->immediate; + dest_off =arch_jump_destination (insn); }else if (rela->sym->type ==STT_SECTION ) { dest_sec = rela->sym->sec; dest_off = rela->addend +4 ;
@@ -668,7 +668,7 @@ static int add_call_destinations(struct objtool_file *file) rela =find_rela_by_dest_range (insn->sec, insn->offset, insn->len);if (!rela) { - dest_off = insn->offset + insn->len + insn->immediate; + dest_off =arch_jump_destination (insn); insn->call_dest =find_symbol_by_offset (insn->sec, dest_off);
@@ -681,14 +681,19 @@ static int add_call_destinations(struct objtool_file *file) } }else if (rela->sym->type ==STT_SECTION ) { +/* +* the original x86_64 code adds 4 to the rela->addend +* which is not needed on arm64 architecture. +*/ + dest_off =arch_dest_rela_offset (rela->addend); insn->call_dest =find_symbol_by_offset (rela->sym->sec, - rela->addend+4 ); + dest_off);if (!insn->call_dest || insn->call_dest->type !=STT_FUNC ) { -WARN_FUNC ("can't find call dest symbol at %s+0x%x" , +WARN_FUNC ("can't find call dest symbol at %s+0x%lx" , insn->sec, insn->offset, rela->sym->sec->name, - rela->addend +4 ); + dest_off);return -1 ; } }else
Signature · 1 line
2.17.1
RFC v2 2/16 objtool: orc: Refactor ORC API for other architectures to implement.
In reply to Raphael GaultThe ORC unwinder is only supported on x86 at the moment and should thus be in the x86 architecture code. In order not to break the whole structure in case another architecture decides to support the ORC unwinder via objtool we choose to let the implementation be done in the architecture dependent code.
---
tools/objtool/Build | 2 -
tools/objtool/arch.h | 3 +
tools/objtool/arch/x86/Build | 2 +
tools/objtool/{ => arch/x86}/orc_dump.c | 4 +-
tools/objtool/{ => arch/x86}/orc_gen.c | 104 ++++++++++++++++++++++--
tools/objtool/check.c | 99 +---------------------
tools/objtool/orc.h | 4 +-
7 files changed, 111 insertions(+), 107 deletions(-)
rename tools/objtool/{ => arch/x86}/orc_dump.c (98%)
rename tools/objtool/{ => arch/x86}/orc_gen.c (69%)tools/objtool/Build +0 -2
@@ -2,8 +2,6 @@ objtool-y += arch/$(SRCARCH)/ objtool-y += builtin-check.o objtool-y += builtin-orc.o objtool-y += check.o -objtool-y += orc_gen.o -objtool-y += orc_dump.o objtool-y += elf.o objtool-y += special.o objtool-y += objtool.o
tools/objtool/arch.h +3 -0
@@ -22,6 +22,7 @@#include <linux/list.h> #include "elf.h" #include "cfi.h" +#include "orc.h" #define INSN_JUMP_CONDITIONAL 1#define INSN_JUMP_UNCONDITIONAL 2
@@ -87,6 +88,8 @@ int arch_decode_instruction(struct elf *elf, struct section *sec,bool arch_callee_saved_reg (unsigned char reg); +int arch_orc_read_unwind_hints (struct objtool_file *file); +unsigned long arch_jump_destination (struct instruction *insn);unsigned long arch_dest_rela_offset (int addend);
tools/objtool/arch/x86/Build +2 -0
@@ -1,4 +1,6 @@ objtool-y += decode.o +objtool-y += orc_dump.o +objtool-y += orc_gen.o inat_tables_script = arch/x86/tools/gen-insn-attr-x86.awk inat_tables_maps = arch/x86/lib/x86-opcode-map.txt
tools/objtool/arch/x86/orc_dump.c renamed from tools/objtool/orc_dump.c +2 -2
@@ -16,8 +16,8 @@*/ #include <unistd.h> -#include "orc.h" -#include "warn.h" +#include "../../orc.h" +#include "../../warn.h" static const char *reg_name (unsigned int reg) {
tools/objtool/arch/x86/orc_gen.c renamed from tools/objtool/orc_gen.c +99 -5
120 lines not on this page · raw message
tools/objtool/check.c +3 -96
120 lines not on this page · raw message
tools/objtool/orc.h +2 -2
@@ -22,8 +22,8 @@struct objtool_file ; -int create_orc (struct objtool_file *file); -int create_orc_sections (struct objtool_file *file); +int arch_create_orc (struct objtool_file *file); +int arch_create_orc_sections (struct objtool_file *file);int orc_dump (const char *objname);
Signature · 1 line
2.17.1
RFC v2 3/16 objtool: Move registers and control flow to arch-dependent code
In reply to Raphael GaultThe control flow information and register macro definitions were based on the x86_64 architecture but should be abstract so that each architecture can define the correct values for the registers, especially the registers related to the stack frame (Frame Pointer, Stack Pointer and possibly Return Address).
---
tools/objtool/arch/x86/include/arch_special.h | 36 +++++++++++++++++++
tools/objtool/{ => arch/x86/include}/cfi.h | 0
tools/objtool/check.h | 1 +
tools/objtool/special.c | 19 +---------
4 files changed, 38 insertions(+), 18 deletions(-)
create mode 100644 tools/objtool/arch/x86/include/arch_special.h
rename tools/objtool/{ => arch/x86/include}/cfi.h (100%)tools/objtool/arch/x86/include/arch_special.h new file +36 -0
@@ -0,0 +1,36 @@ +/* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version 2 +* of the License, or (at your option) any later version. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +* You should have received a copy of the GNU General Public License +* along with this program; if not, see <http://www.gnu.org/licenses/>. +*/ +#ifndef _X86_ARCH_SPECIAL_H +#define _X86_ARCH_SPECIAL_H + +#define EX_ENTRY_SIZE 12 +#define EX_ORIG_OFFSET 0 +#define EX_NEW_OFFSET 4 + +#define JUMP_ENTRY_SIZE 16 +#define JUMP_ORIG_OFFSET 0 +#define JUMP_NEW_OFFSET 4 + +#define ALT_ENTRY_SIZE 13 +#define ALT_ORIG_OFFSET 0 +#define ALT_NEW_OFFSET 4 +#define ALT_FEATURE_OFFSET 8 +#define ALT_ORIG_LEN_OFFSET 10 +#define ALT_NEW_LEN_OFFSET 11 + +#define X86_FEATURE_POPCNT (4 * 32 + 23) +#define X86_FEATURE_SMAP (9 * 32 + 20) + +#endif /* _X86_ARCH_SPECIAL_H */
tools/objtool/arch/x86/include/cfi.h renamed from tools/objtool/cfi.h +0 -0
tools/objtool/check.h +1 -0
@@ -23,6 +23,7 @@#include "cfi.h" #include "arch.h" #include "orc.h" +#include "arch_special.h" #include <linux/hashtable.h> struct insn_state {
tools/objtool/special.c +1 -18
@@ -26,24 +26,7 @@#include "builtin.h" #include "special.h" #include "warn.h" - -#define EX_ENTRY_SIZE 12 -#define EX_ORIG_OFFSET 0 -#define EX_NEW_OFFSET 4 - -#define JUMP_ENTRY_SIZE 16 -#define JUMP_ORIG_OFFSET 0 -#define JUMP_NEW_OFFSET 4 - -#define ALT_ENTRY_SIZE 13 -#define ALT_ORIG_OFFSET 0 -#define ALT_NEW_OFFSET 4 -#define ALT_FEATURE_OFFSET 8 -#define ALT_ORIG_LEN_OFFSET 10 -#define ALT_NEW_LEN_OFFSET 11 - -#define X86_FEATURE_POPCNT (4*32+23) -#define X86_FEATURE_SMAP (9*32+20) +#include "arch_special.h" struct special_entry {const char *sec;
Signature · 1 line
2.17.1
RFC v2 4/16 objtool: arm64: Add required implementation for supporting the aarch64 architecture in objtool.
In reply to Raphael GaultProvide implementation for the arch-dependent functions that are called by the main check function of objtool. The ORC unwinder is not yet supported by the arm64 architecture so we only provide a dummy interface for now. The decoding of the instruction is split into classes and subclasses as described into the Instruction Encoding in the ArmV8.5 Architecture Reference Manual.
In order to handle the load/store instructions for a pair of registers we add an extra field to the stack_op structure.
--- tools/objtool/arch.h | 7 + tools/objtool/arch/arm64/Build | 7 + tools/objtool/arch/arm64/bit_operations.c | 67 + tools/objtool/arch/arm64/decode.c | 2778 +++++++++++++++++ .../objtool/arch/arm64/include/arch_special.h | 36 + .../arch/arm64/include/asm/orc_types.h | 96 + .../arch/arm64/include/bit_operations.h | 24 + tools/objtool/arch/arm64/include/cfi.h | 74 + .../objtool/arch/arm64/include/insn_decode.h | 211 ++ tools/objtool/arch/arm64/orc_dump.c | 26 + tools/objtool/arch/arm64/orc_gen.c | 40 + 11 files changed, 3366 insertions(+) create mode 100644 tools/objtool/arch/arm64/Build create mode 100644 tools/objtool/arch/arm64/bit_operations.c create mode 100644 tools/objtool/arch/arm64/decode.c create mode 100644 tools/objtool/arch/arm64/include/arch_special.h create mode 100644 tools/objtool/arch/arm64/include/asm/orc_types.h create mode 100644 tools/objtool/arch/arm64/include/bit_operations.h create mode 100644 tools/objtool/arch/arm64/include/cfi.h create mode 100644 tools/objtool/arch/arm64/include/insn_decode.h create mode 100644 tools/objtool/arch/arm64/orc_dump.c create mode 100644 tools/objtool/arch/arm64/orc_gen.c
tools/objtool/arch.h +7 -0
@@ -72,9 +72,16 @@ struct op_src {int offset; }; +struct op_extra { +unsigned char used; +unsigned char reg; +int offset; +}; +struct stack_op {struct op_dest dest;struct op_src src; +struct op_extra extra; };struct instruction ;
tools/objtool/arch/arm64/Build new file +7 -0
@@ -0,0 +1,7 @@ +objtool-y += decode.o +objtool-y += orc_dump.o +objtool-y += orc_gen.o +objtool-y += bit_operations.o + + +CFLAGS_decode.o += -I$(OUTPUT)arch/arm64/lib
tools/objtool/arch/arm64/bit_operations.c new file +67 -0
67 lines not on this page · raw message
tools/objtool/arch/arm64/decode.c new file +2778 -0
2,778 lines not on this page · raw message
tools/objtool/arch/arm64/include/arch_special.h new file +36 -0
@@ -0,0 +1,36 @@ +/* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version 2 +* of the License, or (at your option) any later version. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +* You should have received a copy of the GNU General Public License +* along with this program; if not, see <http://www.gnu.org/licenses/>. +*/ +#ifndef _ARM64_ARCH_SPECIAL_H +#define _ARM64_ARCH_SPECIAL_H + +#define EX_ENTRY_SIZE 8 +#define EX_ORIG_OFFSET 0 +#define EX_NEW_OFFSET 4 + +#define JUMP_ENTRY_SIZE 16 +#define JUMP_ORIG_OFFSET 0 +#define JUMP_NEW_OFFSET 4 + +#define ALT_ENTRY_SIZE 12 +#define ALT_ORIG_OFFSET 0 +#define ALT_NEW_OFFSET 4 +#define ALT_FEATURE_OFFSET 8 +#define ALT_ORIG_LEN_OFFSET 10 +#define ALT_NEW_LEN_OFFSET 11 + +#define X86_FEATURE_POPCNT (4 * 32 + 23) +#define X86_FEATURE_SMAP (9 * 32 + 20) + +#endif /* _ARM64_ARCH_SPECIAL_H */
tools/objtool/arch/arm64/include/asm/orc_types.h new file +96 -0
96 lines not on this page · raw message
tools/objtool/arch/arm64/include/bit_operations.h new file +24 -0
Lines of this file are not shown. View the raw message.
tools/objtool/arch/arm64/include/cfi.h new file +74 -0
74 lines not on this page · raw message
tools/objtool/arch/arm64/include/insn_decode.h new file +211 -0
211 lines not on this page · raw message
tools/objtool/arch/arm64/orc_dump.c new file +26 -0
Lines of this file are not shown. View the raw message.
tools/objtool/arch/arm64/orc_gen.c new file +40 -0
Lines of this file are not shown. View the raw message.
The rest of this diff is not shown. View the raw message.
Signature · 1 line
2.17.1
Part of the diff is not shown here. View the raw message.
RFC v2 5/16 objtool: arm64: Handle hypercalls as nops
In reply to Raphael GaultWe consider that the hypervisor/secure-monitor is behaving correctly. This enables us to handle hvc/smc/svc context switching instructions as nop since we consider that the context is restored correctly. This enables us to get rid of the "unsupported instruction in callable function" warning which is not really useful.
Note that those instruction/warnings are caused by hypervisor-related calls.
--- tools/objtool/arch/arm64/decode.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
tools/objtool/arch/arm64/decode.c +5 -2
@@ -577,8 +577,11 @@ int arm_decode_except_gen(u32 instr, unsigned char *type,case INSN_SVC :case INSN_HVC :case INSN_SMC : - *immediate = imm16; - *type =INSN_CONTEXT_SWITCH ; +/* +* We consider that the context will be restored correctly +* with an unchanged sp and the same general registers +*/ + *type =INSN_NOP ;return 0 ;case INSN_BRK :if (imm16 ==0x800 )
Signature · 7 lines
2.17.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
RFC v2 6/16 arm64: alternative: Mark .altinstr_replacement as containing executable instructions
In reply to Raphael GaultUntil now, the section .altinstr_replacement wasn't marked as containing executable instructions on arm64. This patch changes that so that it is coherent with what is done on x86.
--- arch/arm64/include/asm/alternative.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/include/asm/alternative.h +1 -1
@@ -71,7 +71,7 @@ static inline void apply_alternatives_module(void *start, size_t length) { } ALTINSTR_ENTRY(feature,cb) \".popsection\n" \ " .if " __stringify(cb) " == 0\n" \ -".pushsection .altinstr_replacement, \"a\"\n" \ +".pushsection .altinstr_replacement, \"ax\"\n" \"663:\n\t" \ newinstr"\n" \"664:\n\t" \
Signature · 1 line
2.17.1
RFC v2 7/16 objtool: special: Adapt special section handling
In reply to Raphael GaultThis patch abstracts the few architecture dependent tests that are perform when handling special section and switch tables. It enables any architecture to ignore a particular CPU feature or not to handle switch tables.
--- tools/objtool/arch/arm64/Build | 1 + tools/objtool/arch/arm64/include/arch_special.h | 10 ++++++++-- tools/objtool/arch/x86/Build | 1 + tools/objtool/arch/x86/include/arch_special.h | 9 +++++++++ tools/objtool/check.c | 15 +++++++++++++-- tools/objtool/special.c | 9 ++------- tools/objtool/special.h | 3 +++ 7 files changed, 37 insertions(+), 11 deletions(-)
tools/objtool/arch/arm64/Build +1 -0
@@ -1,3 +1,4 @@ +objtool-y += arch_special.o objtool-y += decode.o objtool-y += orc_dump.o objtool-y += orc_gen.o
tools/objtool/arch/arm64/include/arch_special.h +8 -2
@@ -30,7 +30,13 @@#define ALT_ORIG_LEN_OFFSET 10#define ALT_NEW_LEN_OFFSET 11 -#define X86_FEATURE_POPCNT (4 * 32 + 23) -#define X86_FEATURE_SMAP (9 * 32 + 20) +static inline bool arch_should_ignore_feature (unsigned short feature) +{ +return false; +} +static inline bool arch_support_switch_table (void ) +{ +return false; +}#endif /* _ARM64_ARCH_SPECIAL_H */
tools/objtool/arch/x86/Build +1 -0
@@ -1,3 +1,4 @@ +objtool-y += arch_special.o objtool-y += decode.o objtool-y += orc_dump.o objtool-y += orc_gen.o
tools/objtool/arch/x86/include/arch_special.h +9 -0
@@ -33,4 +33,13 @@#define X86_FEATURE_POPCNT (4 * 32 + 23)#define X86_FEATURE_SMAP (9 * 32 + 20) +static inline bool arch_should_ignore_feature (unsigned short feature) +{ +return feature ==X86_FEATURE_POPCNT ; +} + +static inline bool arch_support_switch_table (void ) +{ +return true; +}#endif /* _X86_ARCH_SPECIAL_H */
tools/objtool/check.c +13 -2
@@ -738,7 +738,7 @@ static int handle_group_alt(struct objtool_file *file, last_orig_insn = insn; } -if (next_insn_same_sec (file, last_orig_insn)) { +if (last_orig_insn &&next_insn_same_sec (file, last_orig_insn)) { fake_jump =malloc (sizeof (*fake_jump));if (!fake_jump) {WARN ("malloc failed" );
@@ -1054,6 +1054,17 @@ static struct rela *find_switch_table(struct objtool_file *file,if (find_symbol_containing (rodata_sec, table_offset))continue ; +/* +* If we are on arm64 architecture, we now that we +* are in presence of a switch table thanks to +* the `br <Xn>` insn. but we can't retrieve it yet. +* So we just ignore unreachable for this file. +*/ +if (!arch_support_switch_table ()) { + file->ignore_unreachables = true; +return NULL ; + } + rodata_rela =find_rela_by_dest (rodata_sec, table_offset);if (rodata_rela) {/*
@@ -1853,7 +1864,7 @@ static int validate_branch(struct objtool_file *file, struct instruction *first, insn = first; sec = insn->sec; -if (insn->alt_group &&list_empty (&insn->alts)) { +if (!insn->visited && insn->alt_group &&list_empty (&insn->alts)) {WARN_FUNC ("don't know how to handle branch to middle of alternative instruction group" , sec, insn->offset);return 1 ;
tools/objtool/special.c +2 -7
@@ -93,7 +93,7 @@ static int get_alt_entry(struct elf *elf, struct special_entry *entry,* feature path which is a "very very small percentage of * machines". */ -if (feature ==X86_FEATURE_POPCNT ) +if (arch_should_ignore_feature (feature)) alt->skip_orig = true;/*
@@ -105,12 +105,7 @@ static int get_alt_entry(struct elf *elf, struct special_entry *entry,* find paths that see the STAC but take the NOP instead of * CLAC and the other way around. */ -if (feature ==X86_FEATURE_SMAP ) { -if (uaccess) - alt->skip_orig = true; -else - alt->skip_alt = true; - } +arch_force_alt_path (feature, uaccess, alt); } orig_rela =find_rela_by_dest (sec, offset + entry->orig);
tools/objtool/special.h +3 -0
@@ -39,5 +39,8 @@ struct special_alt { };int special_get_alts (struct elf *elf,struct list_head *alts); +void arch_force_alt_path (unsigned short feature, +bool uaccess, +struct special_alt *alt);#endif /* _SPECIAL_H */
Signature · 1 line
2.17.1
RFC v2 8/16 objtool: arm64: Adapt the stack frame checks for arm architecture
In reply to Raphael GaultSince the way the initial stack frame when entering a function is different that what is done in the x86_64 architecture, we need to add some more check to support the different cases. As opposed as for x86_64, the return address is not stored by the call instruction but is instead loaded in a register. The initial stack frame is thus empty when entering a function and 2 push operations are needed to set it up correctly. All the different combinations need to be taken into account.
--- tools/objtool/arch.h | 2 + tools/objtool/arch/arm64/decode.c | 28 +++++++++ tools/objtool/arch/x86/decode.c | 5 ++ tools/objtool/check.c | 100 ++++++++++++++++++++++++++++-- tools/objtool/elf.c | 3 +- 5 files changed, 131 insertions(+), 7 deletions(-)
tools/objtool/arch.h +2 -0
@@ -101,4 +101,6 @@ unsigned long arch_jump_destination(struct instruction *insn);unsigned long arch_dest_rela_offset (int addend); +bool arch_is_insn_sibling_call (struct instruction *insn); +#endif /* _ARCH_H */
tools/objtool/arch/arm64/decode.c +28 -0
@@ -106,6 +106,34 @@ unsigned long arch_dest_rela_offset(int addend)return addend; } +/* +* In order to know if we are in presence of a sibling +* call and not in presence of a switch table we look +* back at the previous instructions and see if we are +* jumping inside the same function that we are already +* in. +*/ +bool arch_is_insn_sibling_call (struct instruction *insn) +{ +struct instruction *prev; +struct list_head *l; +struct symbol *sym; +list_for_each_prev (l, &insn->list) { + prev = list_entry(l, struct instruction, list); +if (!prev->func || + prev->func->pfunc != insn->func->pfunc) +return false; +if (prev->stack_op.src.reg !=ADR_SOURCE ) +continue ; + sym =find_symbol_containing (insn->sec, insn->immediate); +if (!sym || sym->type !=STT_FUNC ) +return false; +else if (sym->type ==STT_FUNC ) +return true; +break ; + } +return false; +}static int is_arm64 (struct elf *elf) {switch (elf->ehdr.e_machine) {
tools/objtool/arch/x86/decode.c +5 -0
@@ -84,6 +84,11 @@ unsigned long arch_dest_rela_offset(int addend)return addend +4 ; } +bool arch_is_insn_sibling_call (struct instruction *insn) +{ +return true; +} + int arch_decode_instruction(struct elf *elf, struct section *sec, unsigned long offset, unsigned int maxlen, unsigned int *len, unsigned char *type,
tools/objtool/check.c +94 -6
182 lines not on this page · raw message
tools/objtool/elf.c +2 -1
@@ -74,7 +74,8 @@ struct symbol *find_symbol_by_offset(struct section *sec, unsigned long offset)struct symbol *sym;list_for_each_entry (sym, &sec->symbol_list, list) -if (sym->type !=STT_SECTION && +if (sym->type !=STT_NOTYPE && + sym->type !=STT_SECTION && sym->offset == offset)return sym;
Signature · 1 line
2.17.1
RFC v2 9/16 arm64: assembler: Add macro to annotate asm function having non standard stack-frame.
In reply to Raphael GaultSome functions don't have standard stack-frames but are intended this way. In order for objtool to ignore those particular cases we add a macro that enables us to annotate the cases we chose to mark as particular.
--- arch/arm64/include/asm/assembler.h | 13 +++++++++++++ 1 file changed, 13 insertions(+)
arch/arm64/include/asm/assembler.h +13 -0
@@ -760,4 +760,17 @@ USER(\label, ic ivau, \tmp2) // invalidate I line PoU .Lyield_out_\@ : .endm + /* + * This macro is the arm64 assembler equivalent of the + * macro STACK_FRAME_NON_STANDARD define at + * ~/include/linux/frame.h + */ + .macro asm_stack_frame_non_standard func +#ifdef CONFIG_STACK_VALIDATION + .pushsection ".discard.func_stack_frame_non_standard" + .8byte \func + .popsection +#endif + .endm +#endif /* __ASM_ASSEMBLER_H */
Signature · 1 line
2.17.1
RFC v2 10/16 arm64: sleep: Prevent stack frame warnings from objtool
In reply to Raphael GaultThis code doesn't respect the Arm PCS but it is intended this way. Adapting it to respect the PCS would result in altering the behaviour.
In order to suppress objtool's warnings, we setup a stack frame for __cpu_suspend_enter and annotate cpu_resume and _cpu_resume as having non-standard stack frames.
--- arch/arm64/kernel/sleep.S | 4 ++++ 1 file changed, 4 insertions(+)
arch/arm64/kernel/sleep.S +4 -0
@@ -90,6 +90,7 @@ ENTRY(__cpu_suspend_enter) str x0, [x1] add x0, x0, #SLEEP_STACK_DATA_SYSTEM_REGS stp x29, lr, [sp, #-16]! + mov x29, sp bl cpu_do_suspend ldp x29, lr, [sp], #16 mov x0, #1
@@ -146,3 +147,6 @@ ENTRY(_cpu_resume) mov x0, #0 ret ENDPROC(_cpu_resume) + + asm_stack_frame_non_standard cpu_resume + asm_stack_frame_non_standard _cpu_resume
Signature · 1 line
2.17.1
RFC v2 11/16 objtool: arm64: Enable stack validation for arm64
In reply to Raphael Gault--- arch/arm64/Kconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm64/Kconfig +1 -0
@@ -152,6 +152,7 @@ config ARM64 select HAVE_RCU_TABLE_INVALIDATE select HAVE_RSEQ select HAVE_STACKPROTECTOR + select HAVE_STACK_VALIDATION select HAVE_SYSCALL_TRACEPOINTS select HAVE_KPROBES select HAVE_KRETPROBES
Signature · 1 line
2.17.1
RFC v2 12/16 arm64: kvm: Annotate non-standard stack frame functions
In reply to Raphael GaultBoth __guest_entry and __guest_exit functions do not setup a correct stack frame. Because they can be considered as callable functions, even if they are particular cases, we chose to silence the warnings given by objtool by annotating them as non-standard.
--- arch/arm64/kvm/hyp/entry.S | 2 ++ 1 file changed, 2 insertions(+)
arch/arm64/kvm/hyp/entry.S +2 -0
@@ -85,6 +85,7 @@ ENTRY(__guest_enter) eret sb ENDPROC(__guest_enter) +asm_stack_frame_non_standard __guest_enter ENTRY(__guest_exit) // x0: return code
@@ -167,3 +168,4 @@ abort_guest_exit_end: orr x0, x0, x5 1: ret ENDPROC(__guest_exit) +asm_stack_frame_non_standard __guest_exit
Signature · 1 line
2.17.1
RFC v2 13/16 arm64: kernel: Add exception on kuser32 to prevent stack analysis
In reply to Raphael Gaultkuser32 being used for compatibility, it contains a32 instructions which are not recognised by objtool when trying to analyse arm64 object files. Thus, we add an exception to skip validation on this particular file.
--- arch/arm64/kernel/Makefile | 3 +++ 1 file changed, 3 insertions(+)
arch/arm64/kernel/Makefile +3 -0
@@ -29,6 +29,9 @@ $(obj)/%.stub.o: $(obj)/%.o FORCE obj-$(CONFIG_COMPAT) += sys32.o kuser32.o signal32.o \ sys_compat.o + +OBJECT_FILES_NON_STANDARD_kuser32.o := y + obj-$(CONFIG_FUNCTION_TRACER) += ftrace.o entry-ftrace.o obj-$(CONFIG_MODULES) += module.o obj-$(CONFIG_ARM64_MODULE_PLTS) += module-plts.o
Signature · 1 line
2.17.1
RFC v2 14/16 arm64: crypto: Add exceptions for crypto object to prevent stack analysis
In reply to Raphael GaultSome crypto modules contain .word of data in the .text section. Since objtool can't make the distinction between data and incorrect instruction, it gives a warning about the instruction beeing unknown and stops the analysis of the object file.
The exception can be removed if the data are moved to another section or if objtool is tweaked to handle this particular case.
--- arch/arm64/crypto/Makefile | 3 +++ 1 file changed, 3 insertions(+)
arch/arm64/crypto/Makefile +3 -0
@@ -46,9 +46,11 @@ aes-neon-blk-y := aes-glue-neon.o aes-neon.o obj-$(CONFIG_CRYPTO_SHA256_ARM64) += sha256-arm64.o sha256-arm64-y := sha256-glue.o sha256-core.o +OBJECT_FILES_NON_STANDARD_sha256-core.o := y obj-$(CONFIG_CRYPTO_SHA512_ARM64) += sha512-arm64.o sha512-arm64-y := sha512-glue.o sha512-core.o +OBJECT_FILES_NON_STANDARD_sha512-core.o := y obj-$(CONFIG_CRYPTO_CHACHA20_NEON) += chacha-neon.o chacha-neon-y := chacha-neon-core.o chacha-neon-glue.o
@@ -61,6 +63,7 @@ aes-arm64-y := aes-cipher-core.o aes-cipher-glue.o obj-$(CONFIG_CRYPTO_AES_ARM64_BS) += aes-neon-bs.o aes-neon-bs-y := aes-neonbs-core.o aes-neonbs-glue.o +OBJECT_FILES_NON_STANDARD_aes-neonbs-core.o := y CFLAGS_aes-glue-ce.o := -DUSE_V8_CRYPTO_EXTENSIONS
Signature · 1 line
2.17.1
RFC v2 15/16 objtool: Introduce INSN_UNKNOWN type
In reply to Raphael GaultOn arm64 some object files contain data stored in the .text section. This data is interpreted by objtool as instruction but can't be identified as a valid one. In order to keep analysing those files we introduce INSN_UNKNOWN type. The "unknown instruction" warning will thus only be raised if such instructions are uncountered while validating an execution branch.
This change doesn't impact the x86 decoding logic since 0 is still used as a way to specify an unknown type, raising the "unknown instruction" warning during the decoding phase still.
--- tools/objtool/arch.h | 3 ++- tools/objtool/arch/arm64/decode.c | 8 ++++---- tools/objtool/arch/arm64/include/insn_decode.h | 4 ++-- tools/objtool/check.c | 10 +++++++++- 4 files changed, 17 insertions(+), 8 deletions(-)
tools/objtool/arch.h +2 -1
@@ -38,7 +38,8 @@#define INSN_CLAC 12#define INSN_STD 13#define INSN_CLD 14 -#define INSN_OTHER 15 +#define INSN_UNKNOWN 15 +#define INSN_OTHER 16#define INSN_LAST INSN_OTHERenum op_dest_type {
tools/objtool/arch/arm64/decode.c +4 -4
@@ -37,9 +37,9 @@*/ static arm_decode_class aarch64_insn_class_decode_table[] = { [INSN_RESERVED ] = arm_decode_reserved, - [INSN_UNKNOWN ] = arm_decode_unknown, + [INSN_UNALLOC_1 ] = arm_decode_unknown, [INSN_SVE_ENC ] = arm_decode_sve_encoding, - [INSN_UNALLOC ] = arm_decode_unknown, + [INSN_UNALLOC_2 ] = arm_decode_unknown, [INSN_LD_ST_4 ] = arm_decode_ld_st, [INSN_DP_REG_5 ] = arm_decode_dp_reg, [INSN_LD_ST_6 ] = arm_decode_ld_st,
@@ -191,7 +191,7 @@ int arch_decode_instruction(struct elf *elf, struct section *sec,int arm_decode_unknown (u32 instr,unsigned char *type,unsigned long *immediate,struct stack_op *op) { - *type =0 ; + *type =INSN_UNKNOWN ;return 0 ; }
@@ -206,7 +206,7 @@ int arm_decode_reserved(u32 instr, unsigned char *type, unsigned long *immediate, struct stack_op *op) { *immediate = instr &ONES (16 ); - *type =INSN_BUG ; + *type =INSN_UNKNOWN ;return 0 ; }
tools/objtool/arch/arm64/include/insn_decode.h +2 -2
@@ -20,9 +20,9 @@#include "../../../arch.h" #define INSN_RESERVED 0b0000 -#define INSN_UNKNOWN 0b0001 +#define INSN_UNALLOC_1 0b0001#define INSN_SVE_ENC 0b0010 -#define INSN_UNALLOC 0b0011 +#define INSN_UNALLOC_2 0b0011#define INSN_DP_IMM 0b1001 //0x100x#define INSN_BRANCH 0b1011 //0x101x#define INSN_LD_ST_4 0b0100 //0bx1x0
tools/objtool/check.c +9 -1
@@ -1961,6 +1961,13 @@ static int validate_branch(struct objtool_file *file, struct instruction *first,while (1 ) { next_insn =next_insn_same_sec (file, insn); +if (insn->type ==INSN_UNKNOWN ) { +WARN ("%s+0x%lx unknown instruction type, should never be reached" , + insn->sec->name, + insn->offset); +return 1 ; + } +if (file->c_file && func && insn->func && func != insn->func->pfunc) {WARN ("%s() falls through to next function %s()" , func->name, insn->func->name);
@@ -2391,7 +2398,8 @@ static int validate_reachable_instructions(struct objtool_file *file)return 0 ;for_each_insn (file, insn) { -if (insn->visited ||ignore_unreachable_insn (insn)) +if (insn->visited ||ignore_unreachable_insn (insn) || + insn->type ==INSN_UNKNOWN )continue ;WARN_FUNC ("unreachable instruction" , insn->sec, insn->offset);
Signature · 1 line
2.17.1
RFC v2 16/16 arm64: kernel: Annotate non-standard stack frame functions
In reply to Raphael GaultAnnotate assembler functions which are callable but do not setup a correct stack frame.
--- arch/arm64/kernel/hyp-stub.S | 2 ++ arch/arm64/kvm/hyp-init.S | 2 ++ 2 files changed, 4 insertions(+)
arch/arm64/kernel/hyp-stub.S +2 -0
@@ -53,6 +53,7 @@ ENTRY(__hyp_stub_vectors) ventry el1_fiq_invalid // FIQ 32-bit EL1 ventry el1_error_invalid // Error 32-bit EL1 ENDPROC(__hyp_stub_vectors) +asm_stack_frame_non_standard __hyp_stub_vectors .align 11
@@ -80,6 +81,7 @@ el1_sync: 9: mov x0, xzr eret ENDPROC(el1_sync) +asm_stack_frame_non_standard el1_sync .macro invalid_vector label \label:
arch/arm64/kvm/hyp-init.S +2 -0
@@ -129,6 +129,7 @@ CPU_BE( orr x4, x4, #SCTLR_ELx_EE) /* Hello, World! */ eret ENDPROC(__kvm_hyp_init) +asm_stack_frame_non_standard __kvm_hyp_init ENTRY(__kvm_handle_stub_hvc) cmp x0, #HVC_SOFT_RESTART
@@ -170,6 +171,7 @@ reset: eret ENDPROC(__kvm_handle_stub_hvc) +asm_stack_frame_non_standard __kvm_handle_stub_hvc .ltorg
Signature · 1 line
2.17.1
Quoted 4 lines · Raphael Gault
Noteworthy points:
* I still haven't figured out how to detect switch-tables on arm64. I have a better understanding of them but still haven't implemented checks as it doesn't look trivial at all.
Switch tables were tricky to get right on x86. If you share an example (or even just a .o file) I can take a look. Hopefully they're somewhat similar to x86 switch tables. Otherwise we may want to consider a different approach (for example maybe a GCC plugin could help annotate them).
Signature · 1 line
Josh
Hi Josh,
Thanks for offering your help and sorry for the late answer.
My understanding is that a table of offsets is built by GCC, those offsets being scaled by 4 before adding them to the base label. I believe the offsets are stored in the .rodata section. To find the size of that table, it is needed to find a comparison, which can be optimized out apprently. In that case the end of the array can be found by locating labels pointing to data behind it (which is not 100% safe).
Quoted 6 lines · Josh Poimboeuf
Quoted 4 lines · Raphael Gault
Noteworthy points:
* I still haven't figured out how to detect switch-tables on arm64. I have a better understanding of them but still haven't implemented checks as it doesn't look trivial at all.
Quoted 6 lines
Switch tables were tricky to get right on x86. If you share an example (or even just a .o file) I can take a look. Hopefully they're somewhat similar to x86 switch tables. Otherwise we may want to consider a different approach (for example maybe a GCC plugin could help annotate them).
The case which made me realize the issue is the one of arch/arm64/kernel/module.o:apply_relocate_add:
``` What seems to happen in the case of module.o is: 334: 90000015 adrp x21, 0 <do_reloc> which retrieves the location of an offset in the rodata section, and a bit later we do some extra computation with it in order to compute the jump destination: 3e0: 78625aa0 ldrh w0, [x21, w2, uxtw #1] 3e4: 10000061 adr x1, 3f0 <apply_relocate_add+0xf8> 3e8: 8b20a820 add x0, x1, w0, sxth #2 3ec: d61f0000 br x0 ```
Please keep in mind that the actual offsets might vary.
I'm happy to provide more details about what I have identified if you want me to.
Thanks,
--
Raphael Gault
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Quoted 40 lines · Raphael Gault
Hi Josh,
Thanks for offering your help and sorry for the late answer.
My understanding is that a table of offsets is built by GCC, those offsets being scaled by 4 before adding them to the base label. I believe the offsets are stored in the .rodata section. To find the size of that table, it is needed to find a comparison, which can be optimized out apprently. In that case the end of the array can be found by locating labels pointing to data behind it (which is not 100% safe).
Quoted 6 lines · Josh Poimboeuf
Quoted 4 lines · Raphael Gault
Noteworthy points:
* I still haven't figured out how to detect switch-tables on arm64. I have a better understanding of them but still haven't implemented checks as it doesn't look trivial at all.Quoted 6 lines
Switch tables were tricky to get right on x86. If you share an example (or even just a .o file) I can take a look. Hopefully they're somewhat similar to x86 switch tables. Otherwise we may want to consider a different approach (for example maybe a GCC plugin could help annotate them).
The case which made me realize the issue is the one of arch/arm64/kernel/module.o:apply_relocate_add:
``` What seems to happen in the case of module.o is: 334: 90000015 adrp x21, 0 <do_reloc> which retrieves the location of an offset in the rodata section, and a bit later we do some extra computation with it in order to compute the jump destination: 3e0: 78625aa0 ldrh w0, [x21, w2, uxtw #1] 3e4: 10000061 adr x1, 3f0 <apply_relocate_add+0xf8> 3e8: 8b20a820 add x0, x1, w0, sxth #2 3ec: d61f0000 br x0 ```
Quoted 4 lines
Please keep in mind that the actual offsets might vary.
I'm happy to provide more details about what I have identified if you want me to.
Thanks. I'll try to take a deeper look.
Were these patches based on tip/master? There were some minor conflicts in arch/arm64/Kconfig and arch/arm64/kernel/Makefile.
I'm also getting a build failure on arm64:
make[4]: *** No rule to make target '/root/linux/tools/objtool/arch/arm64/arch_special.o', needed by '/root/linux/tools/objtool/arch/arm64/objtool-in.o'. Stop
It looks like arch/arm64/Build and arch/x86/Build are trying to build from arch_special.c which doesn't exist.
Signature · 1 line
Josh
Hi Josh,
Quoted 43 lines · Josh Poimboeuf
Quoted 42 lines · Raphael Gault
Hi Josh,
Thanks for offering your help and sorry for the late answer.
My understanding is that a table of offsets is built by GCC, those offsets being scaled by 4 before adding them to the base label. I believe the offsets are stored in the .rodata section. To find the size of that table, it is needed to find a comparison, which can be optimized out apprently. In that case the end of the array can be found by locating labels pointing to data behind it (which is not 100% safe).
Quoted 6 lines · Josh Poimboeuf
Quoted 4 lines · Raphael Gault
Noteworthy points:
* I still haven't figured out how to detect switch-tables on arm64. I have a better understanding of them but still haven't implemented checks as it doesn't look trivial at all.Quoted 6 lines
Switch tables were tricky to get right on x86. If you share an example (or even just a .o file) I can take a look. Hopefully they're somewhat similar to x86 switch tables. Otherwise we may want to consider a different approach (for example maybe a GCC plugin could help annotate them).
The case which made me realize the issue is the one of arch/arm64/kernel/module.o:apply_relocate_add:
``` What seems to happen in the case of module.o is: 334: 90000015 adrp x21, 0 <do_reloc> which retrieves the location of an offset in the rodata section, and a bit later we do some extra computation with it in order to compute the jump destination: 3e0: 78625aa0 ldrh w0, [x21, w2, uxtw #1] 3e4: 10000061 adr x1, 3f0 <apply_relocate_add+0xf8> 3e8: 8b20a820 add x0, x1, w0, sxth #2 3ec: d61f0000 br x0 ```Please keep in mind that the actual offsets might vary.
Quoted 8 lines
Quoted 2 lines
I'm happy to provide more details about what I have identified if you want me to.
Thanks. I'll try to take a deeper look.
Were these patches based on tip/master? There were some minor conflicts in
arch/arm64/Kconfigandarch/arm64/kernel/Makefile.
These patches were based on tip/core-objtool. I'll base the next version on master. Sorry about that.
Quoted 7 lines
I'm also getting a build failure on arm64:
make[4]: *** No rule to make target '
/root/linux/tools/objtool/arch/arm64/arch_special.o', needed by '/root/linux/tools/objtool/arch/arm64/objtool-in.o'. StopIt looks like
arch/arm64/Buildandarch/x86/Buildare trying to build fromarch_special.cwhich doesn't exist.
Indeed, I apologize deeply for this embarrassing mistake which will be fixed very soon.
Thanks,
--
Raphael Gault
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Hi Josh,
On 5/23/19 12:11 AM, Josh Poimboeuf wrote:
[...]
Quoted 7 lines
I'm also getting a build failure on arm64:
make[4]: *** No rule to make target '
/root/linux/tools/objtool/arch/arm64/arch_special.o', needed by '/root/linux/tools/objtool/arch/arm64/objtool-in.o'. StopIt looks like
arch/arm64/Buildandarch/x86/Buildare trying to build fromarch_special.cwhich doesn't exist.
Please find attach a corrective patch. I am sorry about that. I will integrate this fix correctly in my next version.
Thanks,
--
Raphael Gault
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
From 10ad134841c36ffc60078a9f5a0d69bcebbff175 Mon Sep 17 00:00:00 2001
From: Raphael Gault <[email protected]>
Date: Thu, 23 May 2019 08:56:37 +0100
Subject: [PATCH] objtool: special: Correct mistake missing file
--- tools/objtool/arch/arm64/arch_special.c | 22 +++++++++++++++++++ tools/objtool/arch/x86/arch_special.c | 28 +++++++++++++++++++++++++ 2 files changed, 50 insertions(+) create mode 100644 tools/objtool/arch/arm64/arch_special.c create mode 100644 tools/objtool/arch/x86/arch_special.c
tools/objtool/arch/arm64/arch_special.c new file +22 -0
@@ -0,0 +1,22 @@ +/* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version 2 +* of the License, or (at your option) any later version. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +* You should have received a copy of the GNU General Public License +* along with this program; if not, see <http://www.gnu.org/licenses/>. +*/ +#include "../../special.h" +#include "arch_special.h" + +void arch_force_alt_path (unsigned short feature, +bool uaccess, +struct special_alt *alt) +{ +}
tools/objtool/arch/x86/arch_special.c new file +28 -0
@@ -0,0 +1,28 @@ +/* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version 2 +* of the License, or (at your option) any later version. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +* +* You should have received a copy of the GNU General Public License +* along with this program; if not, see <http://www.gnu.org/licenses/>. +*/ +#include "../../special.h" +#include "arch_special.h" + +void arch_force_alt_path (unsigned short feature, +bool uaccess, +struct special_alt *alt) +{ +if (feature ==X86_FEATURE_SMAP ) { +if (uaccess) + alt->skip_orig = true; +else + alt->skip_alt = true; + } +}
Signature · 1 line
2.17.1
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 40 lines · Raphael Gault
Hi Josh,
Thanks for offering your help and sorry for the late answer.
My understanding is that a table of offsets is built by GCC, those offsets being scaled by 4 before adding them to the base label. I believe the offsets are stored in the .rodata section. To find the size of that table, it is needed to find a comparison, which can be optimized out apprently. In that case the end of the array can be found by locating labels pointing to data behind it (which is not 100% safe).
Quoted 6 lines · Josh Poimboeuf
Quoted 4 lines · Raphael Gault
Noteworthy points:
* I still haven't figured out how to detect switch-tables on arm64. I have a better understanding of them but still haven't implemented checks as it doesn't look trivial at all.Quoted 6 lines
Switch tables were tricky to get right on x86. If you share an example (or even just a .o file) I can take a look. Hopefully they're somewhat similar to x86 switch tables. Otherwise we may want to consider a different approach (for example maybe a GCC plugin could help annotate them).
The case which made me realize the issue is the one of arch/arm64/kernel/module.o:apply_relocate_add:
``` What seems to happen in the case of module.o is: 334: 90000015 adrp x21, 0 <do_reloc> which retrieves the location of an offset in the rodata section, and a bit later we do some extra computation with it in order to compute the jump destination: 3e0: 78625aa0 ldrh w0, [x21, w2, uxtw #1] 3e4: 10000061 adr x1, 3f0 <apply_relocate_add+0xf8> 3e8: 8b20a820 add x0, x1, w0, sxth #2 3ec: d61f0000 br x0 ```
Quoted 4 lines
Please keep in mind that the actual offsets might vary.
I'm happy to provide more details about what I have identified if you want me to.
I get the feeling this is going to be trickier than x86 switch tables (which have already been tricky enough).
On x86, there's a .rela.rodata section which applies relocations to .rodata. The presence of those relocations makes it relatively easy to differentiate switch tables from other read-only data. For example, we can tell that a switch table ends when either a) there's not a text relocation or b) another switch table begins.
But with arm64 I don't see a deterministic way to do that, because the table offsets are hard-coded in .rodata, with no relocations.
From talking with Kamalesh I got the impression that we might have a similar issue for powerpc.
So I'm beginning to think we'll need compiler help. Like a GCC plugin that annotates at least the following switch table metadata:
- Branch instruction address
- Switch table address
- Switch table entry size
- Switch table size
The GCC plugin could write all the above metadata into a special section which gets discarded at link time. I can look at implementing it, though I'll be traveling for two out of the next three weeks so it may be a while before I can get to it.
Signature · 1 line
Josh
Hi Josh,
Quoted 69 lines · Josh Poimboeuf
Quoted 40 lines · Raphael Gault
Hi Josh,
Thanks for offering your help and sorry for the late answer.
My understanding is that a table of offsets is built by GCC, those offsets being scaled by 4 before adding them to the base label. I believe the offsets are stored in the .rodata section. To find the size of that table, it is needed to find a comparison, which can be optimized out apprently. In that case the end of the array can be found by locating labels pointing to data behind it (which is not 100% safe).
Quoted 6 lines · Josh Poimboeuf
Quoted 4 lines · Raphael Gault
Noteworthy points:
* I still haven't figured out how to detect switch-tables on arm64. I have a better understanding of them but still haven't implemented checks as it doesn't look trivial at all.Quoted 6 lines
Switch tables were tricky to get right on x86. If you share an example (or even just a .o file) I can take a look. Hopefully they're somewhat similar to x86 switch tables. Otherwise we may want to consider a different approach (for example maybe a GCC plugin could help annotate them).
The case which made me realize the issue is the one of arch/arm64/kernel/module.o:apply_relocate_add:
``` What seems to happen in the case of module.o is: 334: 90000015 adrp x21, 0 <do_reloc> which retrieves the location of an offset in the rodata section, and a bit later we do some extra computation with it in order to compute the jump destination: 3e0: 78625aa0 ldrh w0, [x21, w2, uxtw #1] 3e4: 10000061 adr x1, 3f0 <apply_relocate_add+0xf8> 3e8: 8b20a820 add x0, x1, w0, sxth #2 3ec: d61f0000 br x0 ```Quoted 4 lines
Please keep in mind that the actual offsets might vary.
I'm happy to provide more details about what I have identified if you want me to.
I get the feeling this is going to be trickier than x86 switch tables (which have already been tricky enough).
On x86, there's a .rela.rodata section which applies relocations to .rodata. The presence of those relocations makes it relatively easy to differentiate switch tables from other read-only data. For example, we can tell that a switch table ends when either a) there's not a text relocation or b) another switch table begins.
But with arm64 I don't see a deterministic way to do that, because the table offsets are hard-coded in .rodata, with no relocations.
From talking with Kamalesh I got the impression that we might have a
similar issue for powerpc.So I'm beginning to think we'll need compiler help. Like a GCC plugin that annotates at least the following switch table metadata:
- Branch instruction address
- Switch table address
- Switch table entry size
- Switch table size
Quoted 5 lines
The GCC plugin could write all the above metadata into a special section which gets discarded at link time. I can look at implementing it, though I'll be traveling for two out of the next three weeks so it may be a while before I can get to it.
I am completely new to GCC plugins but I had a look and I think I found a possible solution to retrieve at least part of this information using the RTL representation in GCC. I can't say it will work for sure but I would be happy to discuss it with you if you want. Although there are still some area I need to investigate related to interacting with the RTL representation and storing info into the ELF
I'd be interested in giving it a try, if you are okay with that.
Thanks,
Signature · 6 lines
Raphael Gault _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 78 lines · Raphael Gault
Hi Josh,
Quoted 69 lines · Josh Poimboeuf
Quoted 40 lines · Raphael Gault
Hi Josh,
Thanks for offering your help and sorry for the late answer.
My understanding is that a table of offsets is built by GCC, those offsets being scaled by 4 before adding them to the base label. I believe the offsets are stored in the .rodata section. To find the size of that table, it is needed to find a comparison, which can be optimized out apprently. In that case the end of the array can be found by locating labels pointing to data behind it (which is not 100% safe).
Quoted 6 lines · Josh Poimboeuf
Quoted 4 lines · Raphael Gault
Noteworthy points:
* I still haven't figured out how to detect switch-tables on arm64. I have a better understanding of them but still haven't implemented checks as it doesn't look trivial at all.Quoted 6 lines
Switch tables were tricky to get right on x86. If you share an example (or even just a .o file) I can take a look. Hopefully they're somewhat similar to x86 switch tables. Otherwise we may want to consider a different approach (for example maybe a GCC plugin could help annotate them).
The case which made me realize the issue is the one of arch/arm64/kernel/module.o:apply_relocate_add:
``` What seems to happen in the case of module.o is: 334: 90000015 adrp x21, 0 <do_reloc> which retrieves the location of an offset in the rodata section, and a bit later we do some extra computation with it in order to compute the jump destination: 3e0: 78625aa0 ldrh w0, [x21, w2, uxtw #1] 3e4: 10000061 adr x1, 3f0 <apply_relocate_add+0xf8> 3e8: 8b20a820 add x0, x1, w0, sxth #2 3ec: d61f0000 br x0 ```Quoted 4 lines
Please keep in mind that the actual offsets might vary.
I'm happy to provide more details about what I have identified if you want me to.
I get the feeling this is going to be trickier than x86 switch tables (which have already been tricky enough).
On x86, there's a .rela.rodata section which applies relocations to .rodata. The presence of those relocations makes it relatively easy to differentiate switch tables from other read-only data. For example, we can tell that a switch table ends when either a) there's not a text relocation or b) another switch table begins.
But with arm64 I don't see a deterministic way to do that, because the table offsets are hard-coded in .rodata, with no relocations.
From talking with Kamalesh I got the impression that we might have a
similar issue for powerpc.So I'm beginning to think we'll need compiler help. Like a GCC plugin that annotates at least the following switch table metadata:
- Branch instruction address
- Switch table address
- Switch table entry size
- Switch table sizeQuoted 5 lines
The GCC plugin could write all the above metadata into a special section which gets discarded at link time. I can look at implementing it, though I'll be traveling for two out of the next three weeks so it may be a while before I can get to it.
Quoted 7 lines
I am completely new to GCC plugins but I had a look and I think I found a possible solution to retrieve at least part of this information using the RTL representation in GCC. I can't say it will work for sure but I would be happy to discuss it with you if you want.
Although there are still some area I need to investigate related to interacting with the RTL representation and storing info into the ELF I'd be interested in giving it a try, if you are okay with that.
Sounds promising. I've been stretched thin lately with other work, and I'll be out again next week, so please go ahead :-)
Signature · 1 line
Josh