From: Will Deacon <will@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Lee Jones <lee.jones@linaro.org>,
Peter Collingbourne <pcc@google.com>,
Michal Marek <michal.lkml@markovi.net>,
Nathan Chancellor <nathan@kernel.org>,
linux-kbuild@vger.kernel.org,
clang-built-linux <clang-built-linux@googlegroups.com>,
linux-arm-kernel@lists.infradead.org,
Elliot Berman <eberman@quicinc.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Fangrui Song <maskray@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Makefile: fix GDB warning with CONFIG_RELR
Date: Tue, 8 Jun 2021 14:21:53 +0100 [thread overview]
Message-ID: <162315417458.2255276.14036371169273697927.b4-ty@kernel.org> (raw)
In-Reply-To: <20210522012626.2811297-1-ndesaulniers@google.com>
On Fri, 21 May 2021 18:26:24 -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.
>
> [...]
Applied to arm64 (for-next/build), thanks!
[1/1] Makefile: fix GDB warning with CONFIG_RELR
https://git.kernel.org/arm64/c/27f2a4db76e8
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Lee Jones <lee.jones@linaro.org>,
Peter Collingbourne <pcc@google.com>,
Michal Marek <michal.lkml@markovi.net>,
Nathan Chancellor <nathan@kernel.org>,
linux-kbuild@vger.kernel.org,
clang-built-linux <clang-built-linux@googlegroups.com>,
linux-arm-kernel@lists.infradead.org,
Elliot Berman <eberman@quicinc.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Fangrui Song <maskray@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Makefile: fix GDB warning with CONFIG_RELR
Date: Tue, 8 Jun 2021 14:21:53 +0100 [thread overview]
Message-ID: <162315417458.2255276.14036371169273697927.b4-ty@kernel.org> (raw)
In-Reply-To: <20210522012626.2811297-1-ndesaulniers@google.com>
On Fri, 21 May 2021 18:26:24 -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.
>
> [...]
Applied to arm64 (for-next/build), thanks!
[1/1] Makefile: fix GDB warning with CONFIG_RELR
https://git.kernel.org/arm64/c/27f2a4db76e8
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-08 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 0:07 [PATCH] Makefile: fix GDB warning with CONFIG_RELR Nick Desaulniers
2021-03-23 19:05 ` Nathan Chancellor
[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-22 1:26 ` Nick Desaulniers
2021-05-26 17:09 ` Will Deacon
2021-05-26 17:09 ` Will Deacon
2021-06-04 18:55 ` Nick Desaulniers
2021-06-04 18:55 ` Nick Desaulniers
2021-06-08 13:21 ` Will Deacon [this message]
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=162315417458.2255276.14036371169273697927.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=eberman@quicinc.com \
--cc=kernel-team@android.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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=nathan@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.