All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Candle Sun <candlesea@gmail.com>,
	Fangrui Song <maskray@google.com>,
	Kees Cook <keescook@chromium.org>, Marco Elver <elver@google.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Sami Tolvanen <samitolvanen@google.com>
Subject: [GIT PULL] Clang feature fixes for v5.13-rc4
Date: Fri, 28 May 2021 10:23:37 -0700	[thread overview]
Message-ID: <202105281022.40F5443A@keescook> (raw)

Hi Linus,

Please pull these Clang feature fixes for v5.13-rc4. One small fix each
for LTO and CFI.

Thanks!

-Kees

The following changes since commit d07f6ca923ea0927a1024dfccafc5b53b61cfecc:

  Linux 5.13-rc2 (2021-05-16 15:27:44 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/clang-features-v5.13-rc4

for you to fetch changes up to 24845dcb170e16b3100bd49743687648c71387ae:

  Makefile: LTO: have linker check -Wframe-larger-than (2021-05-24 15:24:34 -0700)

----------------------------------------------------------------
Clang feature fixes for v5.13-rc4

- Correctly pass stack frame size checking under LTO (Nick Desaulniers)

- Avoid CFI mismatches by checking initcall_t types (Marco Elver)

----------------------------------------------------------------
Marco Elver (1):
      init: verify that function is initcall_t at compile-time

Nick Desaulniers (1):
      Makefile: LTO: have linker check -Wframe-larger-than

 Makefile             | 5 +++++
 include/linux/init.h | 3 ++-
 2 files changed, 7 insertions(+), 1 deletion(-)

-- 
Kees Cook

             reply	other threads:[~2021-05-28 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 17:23 Kees Cook [this message]
2021-05-28 19:00 ` [GIT PULL] Clang feature fixes for v5.13-rc4 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=202105281022.40F5443A@keescook \
    --to=keescook@chromium.org \
    --cc=candlesea@gmail.com \
    --cc=elver@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maskray@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=samitolvanen@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.