Patch "Makefile: fix GDB warning with CONFIG_RELR" has been added to the 5.12-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is a note to let you know that I've just added the patch titled

    Makefile: fix GDB warning with CONFIG_RELR

to the 5.12-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     makefile-fix-gdb-warning-with-config_relr.patch
and it can be found in the queue-5.12 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.



commit 1d688ed0cd58c8e2365029245b07d0f05acfd376
Author: Nick Desaulniers <ndesaulniers@xxxxxxxxxx>
Date:   Fri May 21 18:26:24 2021 -0700

    Makefile: fix GDB warning with CONFIG_RELR
    
    [ Upstream commit 27f2a4db76e8d8a8b601fc1c6a7a17f88bd907ab ]
    
    GDB produces the following warning when debugging kernels built with
    CONFIG_RELR:
    
    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.
    
    Link: https://github.com/ClangBuiltLinux/linux/issues/1057
    Suggested-by: Peter Collingbourne <pcc@xxxxxxxxxx>
    Reviewed-by: Nathan Chancellor <nathan@xxxxxxxxxx>
    Signed-off-by: Nick Desaulniers <ndesaulniers@xxxxxxxxxx>
    Link: https://lore.kernel.org/r/20210522012626.2811297-1-ndesaulniers@xxxxxxxxxx
    Signed-off-by: Will Deacon <will@xxxxxxxxxx>
    Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>

diff --git a/Makefile b/Makefile
index bf6accb2328c..6682790891df 100644
--- a/Makefile
+++ b/Makefile
@@ -1006,7 +1006,7 @@ LDFLAGS_vmlinux	+= $(call ld-option, -X,)
 endif
 
 ifeq ($(CONFIG_RELR),y)
-LDFLAGS_vmlinux	+= --pack-dyn-relocs=relr
+LDFLAGS_vmlinux	+= --pack-dyn-relocs=relr --use-android-relr-tags
 endif
 
 # We never want expected sections to be placed heuristically by the
diff --git a/scripts/tools-support-relr.sh b/scripts/tools-support-relr.sh
index 45e8aa360b45..cb55878bd5b8 100755
--- a/scripts/tools-support-relr.sh
+++ b/scripts/tools-support-relr.sh
@@ -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;
 END
-$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.



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux