mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Kees Cook <kees@kernel.org>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	kernel test robot <lkp@intel.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>
Subject: [GIT PULL] hardening fixes for v6.14-rc2
Date: Sat, 8 Feb 2025 12:43:42 -0800	[thread overview]
Message-ID: <202502081241.8997DC3@keescook> (raw)

Hi Linus,

Please pull these hardening fixes for v6.14-rc2. Addresses a KUnit stack
initialization regression that got tickled on m68k, and solves a Clang
(v14 and earlier) bug found by 0day.

Thanks!

-Kees

The following changes since commit dce4aab8441d285b9a78b33753e0bf583c1320ee:

  kbuild: Use -fzero-init-padding-bits=all (2025-01-30 08:48:34 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.14-rc2

for you to fetch changes up to 6270f4deba3fbd77d1717fb8634f1fc612ff69e2:

  string.h: Use ARRAY_SIZE() for memtostr*()/strtomem*() (2025-02-06 18:48:04 -0800)

----------------------------------------------------------------
hardening fixes for v6.14-rc2

- Fix stackinit KUnit regression on m68k

- Use ARRAY_SIZE() for memtostr*()/strtomem*()

----------------------------------------------------------------
Geert Uytterhoeven (1):
      stackinit: Fix comment for test_small_end

Kees Cook (4):
      stackinit: Keep selftest union size small on m68k
      compiler.h: Move C string helpers into C-only kernel section
      compiler.h: Introduce __must_be_byte_array()
      string.h: Use ARRAY_SIZE() for memtostr*()/strtomem*()

 include/linux/compiler.h | 32 +++++++++++++++++++-------------
 include/linux/string.h   | 12 ++++++++----
 lib/stackinit_kunit.c    |  6 ++++--
 3 files changed, 31 insertions(+), 19 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2025-02-08 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08 20:43 Kees Cook [this message]
2025-02-08 22:25 ` 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=202502081241.8997DC3@keescook \
    --to=kees@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=ojeda@kernel.org \
    --cc=surenb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®