From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Jakub Jelinek <jakub@redhat.com>,
Kees Cook <kees@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>
Subject: [GIT PULL] hardening updates for v6.14-rc1 (fix1)
Date: Fri, 31 Jan 2025 13:38:58 -0800 [thread overview]
Message-ID: <202501311331.B5B6D45@keescook> (raw)
Hi Linus,
Please pull this hardening fix for v6.14-rc1. This is a fix for the soon
to be released GCC 15 which has regressed its initialization of unions
when performing explicit initialization (i.e. a general problem, not
specifically a hardening problem; we're just carrying the fix). Details
in the final patch, Acked by Masahiro, with updated selftests to validate
the fix.
Thanks!
-Kees
The following changes since commit a9a5e0bdc5a77a7c662ad4be0ad661f0b0d5e99d:
hardening: Document INIT_STACK_ALL_PATTERN behavior with GCC (2025-01-08 14:17:33 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.14-rc1-fix1
for you to fetch changes up to dce4aab8441d285b9a78b33753e0bf583c1320ee:
kbuild: Use -fzero-init-padding-bits=all (2025-01-30 08:48:34 -0800)
----------------------------------------------------------------
hardening updates for v6.14-rc1-fix1
- Fix regression in GCC 15's initialization of union members
----------------------------------------------------------------
Kees Cook (3):
stackinit: Add old-style zero-init syntax to struct tests
stackinit: Add union initialization to selftests
kbuild: Use -fzero-init-padding-bits=all
lib/stackinit_kunit.c | 106 +++++++++++++++++++++++++++++++++++++++++++++
scripts/Makefile.extrawarn | 3 ++
2 files changed, 109 insertions(+)
--
Kees Cook
next reply other threads:[~2025-01-31 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 21:38 Kees Cook [this message]
2025-02-01 1:20 ` [GIT PULL] hardening updates for v6.14-rc1 (fix1) 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=202501311331.B5B6D45@keescook \
--to=kees@kernel.org \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@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