From: Nathan Chancellor <nathan@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
clang-built-linux@googlegroups.com,
Fangrui Song <maskray@google.com>,
Elliot Berman <eberman@quicinc.com>,
Sami Tolvanen <samitolvanen@google.com>,
Peter Collingbourne <pcc@google.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Makefile: fix GDB warning with CONFIG_RELR
Date: Tue, 23 Mar 2021 12:05:32 -0700 [thread overview]
Message-ID: <20210323190532.eiqxmskiankf7hn3@archlinux-ax161> (raw)
In-Reply-To: <20210319000708.1694662-1-ndesaulniers@google.com>
On Thu, Mar 18, 2021 at 05:07:06PM -0700, Nick Desaulniers wrote:
> 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@google.com>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> ---
> Makefile | 2 +-
> scripts/tools-support-relr.sh | 3 ++-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 5160ff8903c1..47741cb60995 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1088,7 +1088,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.
> --
> 2.31.0.rc2.261.g7f71774620-goog
>
next prev parent reply other threads:[~2021-03-23 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 0:07 Nick Desaulniers
2021-03-23 19:05 ` Nathan Chancellor [this message]
[not found] ` <CAF2Aj3i3-bev_iS6OrBUTzt==4d0f7UiTeY1YPur6eKFqToFYQ@mail.gmail.com>
2021-05-22 1:06 ` Masahiro Yamada
2021-05-22 1:26 ` [PATCH v2] " Nick Desaulniers
2021-05-26 17:09 ` Will Deacon
2021-06-04 18:55 ` Nick Desaulniers
2021-06-08 13:21 ` Will Deacon
2021-05-24 8:03 ` [PATCH] " Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210323190532.eiqxmskiankf7hn3@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=eberman@quicinc.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=pcc@google.com \
--cc=samitolvanen@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®