From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: kernel-team@android.com, "Will Deacon" <will@kernel.org>,
linux-kernel@vger.kernel.org, "Peter Smith" <Peter.Smith@arm.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Ard Biesheuvel" <ardb@kernel.org>,
"Fāng-ruì Sòng" <maskray@google.com>
Subject: Re: [PATCH] arm64: link with -z norelro regardless of CONFIG_RELOCATABLE
Date: Tue, 20 Oct 2020 18:57:10 +0100 [thread overview]
Message-ID: <160319373854.2175971.17968938488121846972.b4-ty@kernel.org> (raw)
In-Reply-To: <20201016175339.2429280-1-ndesaulniers@google.com>
On Fri, 16 Oct 2020 10:53:39 -0700, Nick Desaulniers wrote:
> With CONFIG_EXPERT=y, CONFIG_KASAN=y, CONFIG_RANDOMIZE_BASE=n,
> CONFIG_RELOCATABLE=n, we observe the following failure when trying to
> link the kernel image with LD=ld.lld:
>
> error: section: .exit.data is not contiguous with other relro sections
>
> ld.lld defaults to -z relro while ld.bfd defaults to -z norelro. This
> was previously fixed, but only for CONFIG_RELOCATABLE=y.
Applied to arm64 (for-next/core), thanks!
[1/1] arm64: link with -z norelro regardless of CONFIG_RELOCATABLE
https://git.kernel.org/arm64/c/3b92fa7485eb
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: Catalin Marinas <catalin.marinas@arm.com>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: "Fāng-ruì Sòng" <maskray@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, "Peter Smith" <Peter.Smith@arm.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
"Will Deacon" <will@kernel.org>,
"Ard Biesheuvel" <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: link with -z norelro regardless of CONFIG_RELOCATABLE
Date: Tue, 20 Oct 2020 18:57:10 +0100 [thread overview]
Message-ID: <160319373854.2175971.17968938488121846972.b4-ty@kernel.org> (raw)
In-Reply-To: <20201016175339.2429280-1-ndesaulniers@google.com>
On Fri, 16 Oct 2020 10:53:39 -0700, Nick Desaulniers wrote:
> With CONFIG_EXPERT=y, CONFIG_KASAN=y, CONFIG_RANDOMIZE_BASE=n,
> CONFIG_RELOCATABLE=n, we observe the following failure when trying to
> link the kernel image with LD=ld.lld:
>
> error: section: .exit.data is not contiguous with other relro sections
>
> ld.lld defaults to -z relro while ld.bfd defaults to -z norelro. This
> was previously fixed, but only for CONFIG_RELOCATABLE=y.
Applied to arm64 (for-next/core), thanks!
[1/1] arm64: link with -z norelro regardless of CONFIG_RELOCATABLE
https://git.kernel.org/arm64/c/3b92fa7485eb
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:[~2020-10-20 17:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 17:53 [PATCH] arm64: link with -z norelro regardless of CONFIG_RELOCATABLE Nick Desaulniers
2020-10-16 17:53 ` Nick Desaulniers
2020-10-20 17:57 ` Will Deacon [this message]
2020-10-20 17:57 ` Will Deacon
2020-10-20 20:16 ` Nick Desaulniers
2020-10-20 20:16 ` Nick Desaulniers
2020-10-21 6:58 ` Ard Biesheuvel
2020-10-21 6:58 ` Ard Biesheuvel
2020-12-14 21:44 ` Nick Desaulniers
2020-12-14 21:44 ` Nick Desaulniers
2020-12-14 23:18 ` Alan Modra
2020-12-14 23:18 ` Alan Modra
2020-12-14 23:33 ` Nick Desaulniers
2020-12-14 23:33 ` Nick Desaulniers
2020-12-17 0:40 ` [PATCH] arm64: link with -z norelro for LLD or aarch64-elf Nick Desaulniers
2020-12-17 0:40 ` Nick Desaulniers
2020-12-17 12:01 ` Will Deacon
2020-12-17 12:01 ` Will Deacon
2020-12-17 21:07 ` Nick Desaulniers
2020-12-17 21:07 ` Nick Desaulniers
2020-12-18 0:24 ` [PATCH v2] " Nick Desaulniers
2020-12-18 0:24 ` Nick Desaulniers
2020-12-18 2:36 ` Nathan Chancellor
2020-12-18 2:36 ` Nathan Chancellor
2021-01-05 12:26 ` Catalin Marinas
2021-01-05 12:26 ` Catalin Marinas
2020-12-17 19:29 ` [PATCH] " Ard Biesheuvel
2020-12-17 19:29 ` Ard Biesheuvel
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=160319373854.2175971.17968938488121846972.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Peter.Smith@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maskray@google.com \
--cc=ndesaulniers@google.com \
--cc=stable@vger.kernel.org \
/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.