From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Kees Cook <keescook@chromium.org>,
kernel test robot <lkp@intel.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: [GIT PULL] kernel hardening fix for v5.19-rc1
Date: Thu, 26 May 2022 08:30:50 -0700 [thread overview]
Message-ID: <202205260827.CADD61804@keescook> (raw)
Hi Linus,
Please pull this kernel hardening fix for v5.19-rc1. This fixes an unlucky
build race condition when using the GCC plugins, noticed by a few folks.
Thanks!
-Kees
The following changes since commit ed5edd5a70b9525085403f193786395179ea303d:
loadpin: stop using bdevname (2022-05-16 16:02:21 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v5.19-rc1-fix1
for you to fetch changes up to d37aa2efc89b387cda93bf15317883519683d435:
gcc-plugins: use KERNELVERSION for plugin version (2022-05-24 08:25:16 -0700)
----------------------------------------------------------------
kernel hardening fix for v5.19-rc1
- Avoid GCC plugins needing utsrelease.h build target (Masahiro Yamada)
----------------------------------------------------------------
Masahiro Yamada (1):
gcc-plugins: use KERNELVERSION for plugin version
scripts/gcc-plugins/Makefile | 2 +-
scripts/gcc-plugins/latent_entropy_plugin.c | 2 +-
scripts/gcc-plugins/randomize_layout_plugin.c | 2 +-
scripts/gcc-plugins/sancov_plugin.c | 2 +-
scripts/gcc-plugins/stackleak_plugin.c | 2 +-
scripts/gcc-plugins/structleak_plugin.c | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
--
Kees Cook
next reply other threads:[~2022-05-26 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 15:30 Kees Cook [this message]
2022-05-27 4:06 ` [GIT PULL] kernel hardening fix for v5.19-rc1 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=202205260827.CADD61804@keescook \
--to=keescook@chromium.org \
--cc=anders.roxell@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).