[lkml]   [2021]   [Jul]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH AUTOSEL 5.12 46/80] Makefile: fix GDB warning with CONFIG_RELR
    From: Nick Desaulniers <>

    [ Upstream commit 27f2a4db76e8d8a8b601fc1c6a7a17f88bd907ab ]

    GDB produces the following warning when debugging kernels built with

    BFD: /android0/linux-next/vmlinux: unknown type [0x13] section `.relr.dyn'

    when loading a kernel built with CONFIG_RELR into GDB. It can also
    prevent debugging symbols using such relocations.

    Peter sugguests:
    [That flag] means that lld will use dynamic tags and section type
    numbers in the OS-specific range rather than the generic range. The
    kernel itself doesn't care about these numbers; it determines the
    location of the RELR section using symbols defined by a linker script.

    Suggested-by: Peter Collingbourne <>
    Reviewed-by: Nathan Chancellor <>
    Signed-off-by: Nick Desaulniers <>
    Signed-off-by: Will Deacon <>
    Signed-off-by: Sasha Levin <>
    Makefile | 2 +-
    scripts/ | 3 ++-
    2 files changed, 3 insertions(+), 2 deletions(-)

    diff --git a/Makefile b/Makefile
    index d2fe36db78ae..657b5db6659d 100644
    --- a/Makefile
    +++ b/Makefile
    @@ -1006,7 +1006,7 @@ LDFLAGS_vmlinux += $(call ld-option, -X,)

    ifeq ($(CONFIG_RELR),y)
    -LDFLAGS_vmlinux += --pack-dyn-relocs=relr
    +LDFLAGS_vmlinux += --pack-dyn-relocs=relr --use-android-relr-tags

    # We never want expected sections to be placed heuristically by the
    diff --git a/scripts/ b/scripts/
    index 45e8aa360b45..cb55878bd5b8 100755
    --- a/scripts/
    +++ b/scripts/
    @@ -7,7 +7,8 @@ trap "rm -f $tmp_file.o $tmp_file $tmp_file.bin" EXIT
    cat << "END" | $CC -c -x c - -o $tmp_file.o >/dev/null 2>&1
    void *p = &p;
    -$LD $tmp_file.o -shared -Bsymbolic --pack-dyn-relocs=relr -o $tmp_file
    +$LD $tmp_file.o -shared -Bsymbolic --pack-dyn-relocs=relr \
    + --use-android-relr-tags -o $tmp_file

    # Despite printing an error message, GNU nm still exits with exit code 0 if it
    # sees a relr section. So we need to check that nothing is printed to stderr.
     \ /
      Last update: 2021-07-05 01:10    [W:4.031 / U:0.204 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site