From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] LTO fix for v5.12-rc6
Date: Thu, 1 Apr 2021 14:39:19 -0700 [thread overview]
Message-ID: <202104011435.78CF22D@keescook> (raw)
Hi Linus,
Please pull this LTO fix for v5.12-rc6. It seems that there is a bug in
ld.bfd when doing module section merging. As explicit merging is only
needed for LTO, the work-around is to only do it under LTO, leaving the
original section layout choices alone under normal builds.
Thanks!
-Kees
The following changes since commit a5e13c6df0e41702d2b2c77c8ad41677ebb065b3:
Linux 5.12-rc5 (2021-03-28 15:48:16 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/lto-v5.12-rc6
for you to fetch changes up to 6a3193cdd5e5b96ac65f04ee42555c216da332af:
kbuild: lto: Merge module sections if and only if CONFIG_LTO_CLANG is enabled (2021-04-01 14:15:59 -0700)
----------------------------------------------------------------
LTO fix for v5.12-rc6
- Only perform explicit module section merges under LTO (Sean Christopherson)
----------------------------------------------------------------
Sean Christopherson (1):
kbuild: lto: Merge module sections if and only if CONFIG_LTO_CLANG is enabled
scripts/module.lds.S | 2 ++
1 file changed, 2 insertions(+)
--
Kees Cook
next reply other threads:[~2021-04-01 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 21:39 Kees Cook [this message]
2021-04-02 1:03 ` [GIT PULL] LTO fix for v5.12-rc6 pr-tracker-bot
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=202104011435.78CF22D@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.com \
--cc=seanjc@google.com \
--cc=torvalds@linux-foundation.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.