All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Kees Cook <kees@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jakub Jelinek <jakub@redhat.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas@fjasle.eu>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	llvm@lists.linux.dev, linux-hardening@vger.kernel.org
Subject: [PATCH v2 0/3] kbuild: Use -fzero-init-padding-bits=all
Date: Mon, 27 Jan 2025 11:10:25 -0800	[thread overview]
Message-ID: <20250127190636.it.745-kees@kernel.org> (raw)

Hi,

This fixes the union initialization regression introduced by GCC 15,
and improves explicit padding initialization for structs.

I can take this via the hardening tree if that's easiest.

-Kees

 v2: Add updated stackinit KUnit tests, improve change log, add Reviewed-By
 v1: https://lore.kernel.org/lkml/20250121003646.work.168-kees@kernel.org/

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(+)

-- 
2.34.1


             reply	other threads:[~2025-01-27 19:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27 19:10 Kees Cook [this message]
2025-01-27 19:10 ` [PATCH v2 1/3] stackinit: Add old-style zero-init syntax to struct tests Kees Cook
2025-01-27 19:10 ` [PATCH v2 2/3] stackinit: Add union initialization to selftests Kees Cook
2025-01-28  7:46   ` Geert Uytterhoeven
2025-02-03 14:44   ` Geert Uytterhoeven
2025-02-04 15:42     ` Kees Cook
2025-01-27 19:10 ` [PATCH v2 3/3] kbuild: Use -fzero-init-padding-bits=all Kees Cook
2025-01-27 19:54   ` Kees Cook
2025-01-30  2:35   ` Masahiro Yamada

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=20250127190636.it.745-kees@kernel.org \
    --to=kees@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=jakub@redhat.com \
    --cc=justinstitt@google.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    /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.