From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "Ewan D. Milne" <emilne@redhat.com>,
Kees Cook <kees@kernel.org>, Marco Patalano <mpatalan@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: [GIT PULL] hardening fixes for v6.10-rc2 (take2)
Date: Sun, 2 Jun 2024 00:23:40 -0700 [thread overview]
Message-ID: <202406020021.3B4B59F3A@keescook> (raw)
Hi Linus,
Please pull these few hardening fixes for v6.10-rc2 (take 2: now with
my regular key).
Thanks!
-Kees
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.10-rc2-take2
for you to fetch changes up to 99a6087dfdc65303d26ab5fba2dacd8931b82b08:
kunit/fortify: Remove __kmalloc_node() test (2024-05-31 13:47:41 -0700)
----------------------------------------------------------------
hardening fixes for v6.10-rc2-take2
- scsi: mpt3sas: Avoid possible run-time warning with long manufacturer strings
- mailmap: update entry for Kees Cook
- kunit/fortify: Remove __kmalloc_node() test
----------------------------------------------------------------
Kees Cook (3):
scsi: mpt3sas: Avoid possible run-time warning with long manufacturer strings
mailmap: update entry for Kees Cook
kunit/fortify: Remove __kmalloc_node() test
.mailmap | 9 +++++----
drivers/scsi/mpt3sas/mpt3sas_base.c | 2 +-
drivers/scsi/mpt3sas/mpt3sas_transport.c | 14 +++++---------
lib/fortify_kunit.c | 3 ---
4 files changed, 11 insertions(+), 17 deletions(-)
--
Kees Cook
reply other threads:[~2024-06-02 7:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202406020021.3B4B59F3A@keescook \
--to=kees@kernel.org \
--cc=emilne@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatalan@redhat.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