scripts/kallsyms: Ignore symbol type 'n'
PATCH 1/1 scripts/kallsyms: Ignore symbol type 'n'
gcc on aarch64 may emit synbols of type 'n' if the kernel is built with '-frecord-gcc-switches'. In most cases, those symbols are reported with nm as
000000000000000e n $d and with objdump as 0000000000000000 l d .GCC.command.line 0000000000000000 .GCC.command.line 000000000000000e l .GCC.command.line 0000000000000000 $d
Those symbols are detected in is_arm_mapping_symbol() and ignored. However, if "--prefix-symbols=<prefix>" is configured as well, the situation is different. For example, in efi/libstub, arm64 images are built with
'--prefix-alloc-sections=.init --prefix-symbols=__efistub_'. In combination with '-frecord-gcc-switches', the symbols are now reported by nm as: 000000000000000e n __efistub_$d and by objdump as: 0000000000000000 l d .GCC.command.line 0000000000000000 .GCC.command.line 000000000000000e l .GCC.command.line 0000000000000000 __efistub_$d
Those symbols are no longer ignored and included in the base address calculation. This results in a base address of 000000000000000e, which in turn causes kallsyms to abort with
kallsyms failure: relative symbol value 0xffffff900800a000 out of range in relative mode
The problem is seen in little endian arm64 builds with CONFIG_EFI enabled and with '-frecord-gcc-switches' set in KCFLAGS.
Explicitly ignore symbols of type 'n' since those are clearly debug symbols.
--- scripts/kallsyms.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
scripts/kallsyms.c +1 -1
@@ -158,7 +158,7 @@ static int read_symbol(FILE *in, struct sym_entry *s)else if (str[0 ] =='$' )return -1 ;/* exclude debugging symbols */ -else if (stype =='N' ) +else if (stype =='N' || stype =='n' )return -1 ;/* include the type field in the symbol name, so that it gets
Signature · 1 line
2.7.4
Quoted 42 lines · Guenter Roeck
gcc on aarch64 may emit synbols of type 'n' if the kernel is built with '-frecord-gcc-switches'. In most cases, those symbols are reported with nm as
000000000000000e n $d and with objdump as 0000000000000000 l d .GCC.command.line 0000000000000000 .GCC.command.line 000000000000000e l .GCC.command.line 0000000000000000 $dThose symbols are detected in
is_arm_mapping_symbol()and ignored. However, if "--prefix-symbols=<prefix>" is configured as well, the situation is different. For example, in efi/libstub, arm64 images are built with'--prefix-alloc-sections=.init --prefix-symbols=__efistub_'. In combination with '-frecord-gcc-switches', the symbols are now reported by nm as: 000000000000000e n __efistub_$d and by objdump as: 0000000000000000 l d .GCC.command.line 0000000000000000 .GCC.command.line 000000000000000e l .GCC.command.line 0000000000000000 __efistub_$dThose symbols are no longer ignored and included in the base address calculation. This results in a base address of
000000000000000e, which in turn causes kallsyms to abort withkallsyms failure: relative symbol value 0xffffff900800a000 out of range in relative modeThe problem is seen in little endian arm64 builds with
CONFIG_EFIenabled and with '-frecord-gcc-switches' set in KCFLAGS.Explicitly ignore symbols of type 'n' since those are clearly debug symbols.
Cc Josh Poimboeuf <[email protected]>Signed-off-by Guenter Roeck <[email protected]>--- scripts/kallsyms.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)scripts/kallsyms.c +0
-0
scripts/kallsyms.c static int read_symbol(FILE *in, struct sym_entry *s) · line 164
Quoted 8 lines
scripts/kallsyms.c +1
-1@@ -158,7 +158,7 @@ static int read_symbol(FILE *in, struct sym_entry *s)else if (str[0 ] =='$' )return -1 ;/* exclude debugging symbols */ -else if (stype =='N' ) +else if (stype =='N' || stype =='n' )return -1 ;/* include the type field in the symbol name, so that it gets