From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tom Saeger <tom.saeger@oracle.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, "H.J. Lu" <hjl.tools@gmail.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 5.4 v3 1/6] x86, vmlinux.lds: Add RUNTIME_DISCARD_EXIT to generic DISCARDS
Date: Wed, 15 Mar 2023 09:39:35 +0100 [thread overview]
Message-ID: <ZBGER4HqDnvotSNg@kroah.com> (raw)
In-Reply-To: <20230210-tsaeger-upstream-linux-stable-5-4-v3-1-122fc5440d4c@oracle.com>
On Wed, Mar 01, 2023 at 07:06:59PM -0700, Tom Saeger wrote:
> From: "H.J. Lu" <hjl.tools@gmail.com>
>
> commit 84d5f77fc2ee4e010c2c037750e32f06e55224b0 upstream.
>
> In the x86 kernel, .exit.text and .exit.data sections are discarded at
> runtime, not by the linker. Add RUNTIME_DISCARD_EXIT to generic DISCARDS
> and define it in the x86 kernel linker script to keep them.
>
> The sections are added before the DISCARD directive so document here
> only the situation explicitly as this change doesn't have any effect on
> the generated kernel. Also, other architectures like ARM64 will use it
> too so generalize the approach with the RUNTIME_DISCARD_EXIT define.
>
> [ bp: Massage and extend commit message. ]
>
> Signed-off-by: H.J. Lu <hjl.tools@gmail.com>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Reviewed-by: Kees Cook <keescook@chromium.org>
> Link: https://lkml.kernel.org/r/20200326193021.255002-1-hjl.tools@gmail.com
> Signed-off-by: Tom Saeger <tom.saeger@oracle.com>
The encoding of this email was very odd, with dos line-ends? Something
was odd on your side, all the others were fine. I've fixed it up...
strange,
greg k-h
next prev parent reply other threads:[~2023-03-15 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 2:06 [PATCH 5.4 v3 0/6] Fix Build ID on arm64 if CONFIG_MODVERSIONS=y Tom Saeger
2023-03-02 2:06 ` [PATCH 5.4 v3 1/6] x86, vmlinux.lds: Add RUNTIME_DISCARD_EXIT to generic DISCARDS Tom Saeger
2023-03-15 8:39 ` Greg Kroah-Hartman [this message]
2023-03-15 14:30 ` Tom Saeger
2023-03-02 2:07 ` [PATCH 5.4 v3 2/6] arch: fix broken BuildID for arm64 and riscv Tom Saeger
2023-03-02 2:07 ` [PATCH 5.4 v3 3/6] powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT Tom Saeger
2023-03-02 2:07 ` [PATCH 5.4 v3 4/6] powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds Tom Saeger
2023-03-02 2:07 ` [PATCH 5.4 v3 5/6] s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 Tom Saeger
2023-03-02 2:07 ` [PATCH 5.4 v3 6/6] sh: define RUNTIME_DISCARD_EXIT Tom Saeger
2023-03-15 8:40 ` [PATCH 5.4 v3 0/6] Fix Build ID on arm64 if CONFIG_MODVERSIONS=y Greg Kroah-Hartman
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=ZBGER4HqDnvotSNg@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hjl.tools@gmail.com \
--cc=keescook@chromium.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tom.saeger@oracle.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.