kallsyms: Get rid of kallsyms relative base
Subsystems (2)
PATCH 1/1 kallsyms: Get rid of kallsyms relative base
From: Ard Biesheuvel <[email protected]>
When the kallsyms relative base was introduced, per-CPU variable references on x86_64 SMP were implemented as offsets into the respective per-CPU region, rather than offsets relative to the location of the variable's template in the kernel image, which is how other architectures implement it.
This required kallsyms to reason about the difference between the two, and the sign of the value in the kallsyms_offsets[] array was used to distinguish them. This meant that negative offsets were not permitted for ordinary variables, and so it was crucial that the relative base was chosen such that all offsets were positive numbers.
This is no longer needed: instead, the offsets can simply be encoded as values in the range -/+ 2 GiB, which is precisely what PC32 relocations provide on most architectures. So it is possible to simplify the logic, and just use _text as the anchor directly, and let the linker calculate the final value based on the location of the entry itself.
Some toy architectures do not support place-relative relocations at all, but these are all 32-bit, and on those architectures, there is no need for place-relative relocations in the first place, and the actual symbol value can just be stored directly.
This makes all entries in the kallsyms_offsets[] array visible as place-relative references in the ELF metadata, which will be important when implementing ELF-based fg-kaslr.
--- kernel/kallsyms.c | 6 +- kernel/kallsyms_internal.h | 1 - kernel/vmcore_info.c | 1 - scripts/kallsyms.c | 64 ++++++-------------- scripts/link-vmlinux.sh | 4 ++ tools/perf/tests/vmlinux-kallsyms.c | 1 - 6 files changed, 25 insertions(+), 52 deletions(-)
kernel/kallsyms.c +4 -2
@@ -151,8 +151,10 @@ static unsigned int get_symbol_offset(unsigned long pos)unsigned long kallsyms_sym_address (int idx) { -/* values are unsigned offsets */ -return kallsyms_relative_base + (u32 )kallsyms_offsets[idx]; +/* non-relocatable 32-bit kernels just embed the value directly */ +if (!IS_ENABLED (CONFIG_64BIT ) && !IS_ENABLED (CONFIG_RELOCATABLE )) +return (u32 )kallsyms_offsets[idx]; +return (unsigned long )offset_to_ptr (kallsyms_offsets + idx); }static unsigned int get_symbol_seq (int index)
kernel/kallsyms_internal.h +0 -1
@@ -8,7 +8,6 @@ extern const int kallsyms_offsets[];extern const u8 kallsyms_names[];extern const unsigned int kallsyms_num_syms; -extern const unsigned long kallsyms_relative_base;extern const char kallsyms_token_table[];extern const u16 kallsyms_token_index[];
kernel/vmcore_info.c +0 -1
@@ -238,7 +238,6 @@ static int __init crash_save_vmcoreinfo_init(void)VMCOREINFO_SYMBOL (kallsyms_token_table);VMCOREINFO_SYMBOL (kallsyms_token_index);VMCOREINFO_SYMBOL (kallsyms_offsets); -VMCOREINFO_SYMBOL (kallsyms_relative_base);#endif /* CONFIG_KALLSYMS */ arch_crash_save_vmcoreinfo ();
scripts/kallsyms.c +17 -47
115 lines not on this page · raw message
scripts/link-vmlinux.sh +4 -0
@@ -143,6 +143,10 @@ kallsyms() kallsymopt="${kallsymopt} --all-symbols" fi + if is_enabled CONFIG_64BIT || is_enabled CONFIG_RELOCATABLE; then + kallsymopt="${kallsymopt} --pc-relative" + fi + info KSYMS "${2}.S" scripts/kallsyms ${kallsymopt} "${1}" > "${2}.S"
tools/perf/tests/vmlinux-kallsyms.c +0 -1
@@ -27,7 +27,6 @@ static bool is_ignored_symbol(const char *name, char type)* stable symbol list. */ "kallsyms_offsets" , -"kallsyms_relative_base" ,"kallsyms_num_syms" ,"kallsyms_names" , "kallsyms_markers",
Signature · 1 line
2.52.0.457.g6b5491de43-goog
Quoted 3 lines · Ard Biesheuvel
This makes all entries in the kallsyms_offsets[] array visible as place-relative references in the ELF metadata, which will be important when implementing ELF-based fg-kaslr.
This makes things a lot simpler.
Signature · 1 line
Kees Cook