From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
clang-built-linux@googlegroups.com, glider@google.com,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-security-module@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [GIT PULL] hardening updates for v5.15-rc1
Date: Mon, 30 Aug 2021 11:27:55 -0700 [thread overview]
Message-ID: <202108301127.836C1F4D@keescook> (raw)
Hi Linus,
Please pull these hardening updates for v5.15-rc1.
Thanks!
-Kees
The following changes since commit 2734d6c1b1a089fb593ef6a23d4b70903526fe0c:
Linux 5.14-rc2 (2021-07-18 14:13:49 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v5.15-rc1
for you to fetch changes up to a8fc576d4af2f23a87a586424252df97f0ad0b06:
lib/test_stackinit: Add assigned initializers (2021-08-22 00:21:36 -0700)
----------------------------------------------------------------
hardening updates for v5.15-rc1
- Expand lib/test_stackinit to include more initialization styles
- Improve Kconfig for CLang's auto-var-init feature
- Introduce support for GCC's zero-call-used-regs feature
----------------------------------------------------------------
Kees Cook (5):
hardening: Introduce CONFIG_ZERO_CALL_USED_REGS
hardening: Clarify Kconfig text for auto-var-init
lib/test_stackinit: Fix static initializer test
lib/test_stackinit: Allow building stand-alone
lib/test_stackinit: Add assigned initializers
Makefile | 5 +
lib/test_stackinit.c | 253 +++++++++++++++++++++++++++++++++------------
security/Kconfig.hardening | 71 +++++++++----
3 files changed, 242 insertions(+), 87 deletions(-)
--
Kees Cook
next reply other threads:[~2021-08-30 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 18:27 Kees Cook [this message]
2021-09-02 20:05 ` [GIT PULL] hardening updates for v5.15-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=202108301127.836C1F4D@keescook \
--to=keescook@chromium.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=glider@google.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@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.