From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Haofeng Li <lihaofeng@kylinos.cn>,
Jiri Olsa <jolsa@kernel.org>, Kees Cook <kees@kernel.org>,
Kuan-Ying Lee <kuan-ying.lee@canonical.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: [GIT PULL] hardening fixes for v7.2-rc6
Date: Tue, 28 Jul 2026 09:30:50 -0700 [thread overview]
Message-ID: <202607280930.A9269E72B@keescook> (raw)
Hi Linus,
Please pull these few hardening fixes for v7.2-rc6.
Thanks!
-Kees
The following changes since commit 8cdeaa50eae8dad34885515f62559ee83e7e8dda:
Linux 7.2-rc2 (2026-07-05 14:44:06 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v7.2-rc6
for you to fetch changes up to 3421b9b056a6576d0ebac1030eafb48ad0544092:
selftests/seccomp: Fix pointer type mismatch build error (2026-07-15 18:11:29 -0700)
----------------------------------------------------------------
hardening fixes for v7.2-rc6
- lkdtm: fix missed rename of STACKLEAK_ERASING to KSTACK_ERASE
(Haofeng Li)
- selftests/seccomp: Fix pointer type mismatch build error
(Kuan-Ying Lee)
- tests/fortify: Disable -Wstringop-overread (Nathan Chancellor)
----------------------------------------------------------------
Haofeng Li (1):
selftests/lkdtm: rename STACKLEAK_ERASING to KSTACK_ERASE
Kuan-Ying Lee (1):
selftests/seccomp: Fix pointer type mismatch build error
Nathan Chancellor (1):
fortify: Disable -Wstringop-overread in tests
lib/test_fortify/Makefile | 1 +
tools/testing/selftests/seccomp/seccomp_bpf.c | 3 ++-
tools/testing/selftests/lkdtm/tests.txt | 2 +-
3 files changed, 4 insertions(+), 2 deletions(-)
--
Kees Cook
next reply other threads:[~2026-07-28 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 16:30 Kees Cook [this message]
2026-07-28 20:56 ` 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=202607280930.A9269E72B@keescook \
--to=kees@kernel.org \
--cc=jolsa@kernel.org \
--cc=kuan-ying.lee@canonical.com \
--cc=lihaofeng@kylinos.cn \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®