The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>,
	Ingo Saitz <ingo@hannover.ccc.de>, Kees Cook <kees@kernel.org>,
	kernel test robot <oliver.sang@intel.com>,
	Marco Elver <elver@google.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Subject: [GIT PULL] hardening fixes for v6.16-rc1
Date: Sat, 31 May 2025 08:00:14 -0700	[thread overview]
Message-ID: <202505310759.3A40AD051@keescook> (raw)

Hi Linus,

Please pull this small handful of hardening fixes for v6.16-rc1.

Thanks!

-Kees

The following changes since commit f8b59a0f90a2adfce5a9206ce5589ed0dc19543c:

  Merge tag 'driver-core-6.16-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core (2025-05-29 09:11:39 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.16-rc1-fix1

for you to fetch changes up to 7ea1ca94c1278615c55a9f61f63d2286b1b10853:

  randstruct: gcc-plugin: Fix attribute addition (2025-05-31 07:51:14 -0700)

----------------------------------------------------------------
hardening fixes for v6.16-rc1

- randstruct: gcc-plugin: Fix attribute addition with GCC 15

- ubsan: integer-overflow: depend on BROKEN to keep this out of CI

- overflow: Introduce __DEFINE_FLEX for having no initializer

- wifi: iwlwifi: mld: Work around Clang loop unrolling bug

----------------------------------------------------------------
Kees Cook (4):
      wifi: iwlwifi: mld: Work around Clang loop unrolling bug
      ubsan: integer-overflow: depend on BROKEN to keep this out of CI
      overflow: Introduce __DEFINE_FLEX for having no initializer
      randstruct: gcc-plugin: Fix attribute addition

 lib/Kconfig.ubsan                             |  2 ++
 scripts/gcc-plugins/gcc-common.h              | 32 +++++++++++++++++++++++++++
 scripts/gcc-plugins/randomize_layout_plugin.c | 22 +++++++++---------
 include/linux/overflow.h                      | 25 ++++++++++++++++-----
 drivers/net/wireless/intel/iwlwifi/mld/d3.c   |  2 +-
 5 files changed, 65 insertions(+), 18 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2025-05-31 15:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-31 15:00 Kees Cook [this message]
2025-05-31 18:20 ` [GIT PULL] hardening fixes for v6.16-rc1 Linus Torvalds
2025-05-31 19:21   ` Konstantin Ryabitsev
2025-05-31 19:57   ` Konstantin Ryabitsev
2025-05-31 21:36   ` Al Viro
2025-06-01  1:06   ` Kees Cook
2025-06-01  2:22     ` Stephen Rothwell
2025-06-01  2:35     ` Linus Torvalds
2025-06-01  5:42       ` Kees Cook
2025-06-01  7:42       ` Kees Cook
2025-06-01 14:40         ` Konstantin Ryabitsev
2025-06-01 15:38           ` Kees Cook
2025-06-01 17:58             ` Konstantin Ryabitsev
2025-06-01 18:56               ` Kees Cook
2025-06-03 12:55               ` Vlastimil Babka
2025-06-01 17:12           ` Linus Torvalds
2025-06-01 17:49             ` Konstantin Ryabitsev
2025-06-01 18:24               ` Linus Torvalds
2025-06-03 12:42             ` Christian Brauner

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=202505310759.3A40AD051@keescook \
    --to=kees@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=elver@google.com \
    --cc=ingo@hannover.ccc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=oliver.sang@intel.com \
    --cc=thiago.bauermann@linaro.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