public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Ryan Roberts <ryan.roberts@arm.com>
Subject: [GIT PULL] hardening updates for v7.1-rc1
Date: Mon, 13 Apr 2026 16:21:45 -0700	[thread overview]
Message-ID: <202604131621.7378BA7@keescook> (raw)

Hi Linus,

Please pull these hardening updates for v7.1-rc1.

Thanks!

-Kees

The following changes since commit 11439c4635edd669ae435eec308f4ab8a0804808:

  Linux 7.0-rc2 (2026-03-01 15:39:31 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v7.1-rc1

for you to fetch changes up to cf2f06f7152d5e38a87aa2e9b8b452714789f6ba:

  lkdtm/fortify: Drop unneeded FORTIFY_STR_OBJECT test (2026-03-31 16:53:47 -0700)

----------------------------------------------------------------
hardening updates for v7.1-rc1

- randomize_kstack: Improve implementation across arches (Ryan Roberts)

- lkdtm/fortify: Drop unneeded FORTIFY_STR_OBJECT test

- refcount: Remove unused __signed_wrap function annotations

----------------------------------------------------------------
Kees Cook (2):
      refcount: Remove unused __signed_wrap function annotations
      lkdtm/fortify: Drop unneeded FORTIFY_STR_OBJECT test

Ryan Roberts (2):
      randomize_kstack: Maintain kstack_offset per task
      randomize_kstack: Unify random source across arches

 arch/Kconfig                            |  5 ++-
 arch/s390/include/asm/entry-common.h    |  8 -----
 arch/x86/include/asm/entry-common.h     | 12 --------
 include/linux/compiler_types.h          |  9 +-----
 include/linux/randomize_kstack.h        | 54 ++++++++++++---------------------
 include/linux/refcount.h                | 10 +++---
 arch/arm64/kernel/syscall.c             | 11 -------
 arch/loongarch/kernel/syscall.c         | 11 -------
 arch/powerpc/kernel/syscall.c           | 16 ++--------
 arch/riscv/kernel/traps.c               | 12 --------
 arch/s390/kernel/syscall.c              |  2 +-
 arch/x86/entry/syscall_32.c             |  4 +--
 arch/x86/entry/syscall_64.c             |  2 +-
 drivers/misc/lkdtm/fortify.c            | 36 ++++------------------
 init/main.c                             |  9 +++++-
 kernel/fork.c                           |  1 +
 tools/testing/selftests/lkdtm/tests.txt |  1 -
 17 files changed, 49 insertions(+), 154 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2026-04-13 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 23:21 Kees Cook [this message]
2026-04-14  0:57 ` [GIT PULL] hardening updates for v7.1-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=202604131621.7378BA7@keescook \
    --to=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ryan.roberts@arm.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