All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>
Cc: kernel-team <kernel-team@android.com>,
	"kernelci . org bot" <bot@kernelci.org>,
	linux-arm-kernel@lists.infradead.org,
	"Fāng-ruì Sòng" <maskray@google.com>,
	"Alan Modra" <amodra@gmail.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Peter Smith" <Peter.Smith@arm.com>,
	"Quentin Perret" <qperret@google.com>,
	linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH v2] arm64: link with -z norelro for LLD or aarch64-elf
Date: Tue,  5 Jan 2021 12:26:03 +0000	[thread overview]
Message-ID: <160984952218.5069.304716966175823056.b4-ty@arm.com> (raw)
In-Reply-To: <20201218002432.788499-1-ndesaulniers@google.com>

On Thu, 17 Dec 2020 16:24:32 -0800, Nick Desaulniers wrote:
> With GNU binutils 2.35+, linking with BFD produces warnings for vmlinux:
> aarch64-linux-gnu-ld: warning: -z norelro ignored
> 
> BFD can produce this warning when the target emulation mode does not
> support RELRO program headers, and -z relro or -z norelro is passed.
> 
> Alan Modra clarifies:
>   The default linker emulation for an aarch64-linux ld.bfd is
>   -maarch64linux, the default for an aarch64-elf linker is
>   -maarch64elf.  They are not equivalent.  If you choose -maarch64elf
>   you get an emulation that doesn't support -z relro.
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64: link with -z norelro for LLD or aarch64-elf
      https://git.kernel.org/arm64/c/311bea3cb9ee

Also added the second Fixes tag with a cc stable.

-- 
Catalin


WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>
Cc: "Fāng-ruì Sòng" <maskray@google.com>,
	"kernelci . org bot" <bot@kernelci.org>,
	"Alan Modra" <amodra@gmail.com>,
	"Quentin Perret" <qperret@google.com>,
	"Peter Smith" <Peter.Smith@arm.com>,
	stable <stable@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	kernel-team <kernel-team@android.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: link with -z norelro for LLD or aarch64-elf
Date: Tue,  5 Jan 2021 12:26:03 +0000	[thread overview]
Message-ID: <160984952218.5069.304716966175823056.b4-ty@arm.com> (raw)
In-Reply-To: <20201218002432.788499-1-ndesaulniers@google.com>

On Thu, 17 Dec 2020 16:24:32 -0800, Nick Desaulniers wrote:
> With GNU binutils 2.35+, linking with BFD produces warnings for vmlinux:
> aarch64-linux-gnu-ld: warning: -z norelro ignored
> 
> BFD can produce this warning when the target emulation mode does not
> support RELRO program headers, and -z relro or -z norelro is passed.
> 
> Alan Modra clarifies:
>   The default linker emulation for an aarch64-linux ld.bfd is
>   -maarch64linux, the default for an aarch64-elf linker is
>   -maarch64elf.  They are not equivalent.  If you choose -maarch64elf
>   you get an emulation that doesn't support -z relro.
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64: link with -z norelro for LLD or aarch64-elf
      https://git.kernel.org/arm64/c/311bea3cb9ee

Also added the second Fixes tag with a cc stable.

-- 
Catalin


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-01-05 12:27 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
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 [this message]
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=160984952218.5069.304716966175823056.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Peter.Smith@arm.com \
    --cc=amodra@gmail.com \
    --cc=ardb@kernel.org \
    --cc=bot@kernelci.org \
    --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=qperret@google.com \
    --cc=stable@vger.kernel.org \
    --cc=will@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.