All of lore.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>,
	Nathan Chancellor <nathan@kernel.org>
Subject: [GIT PULL] hardening fixes for v6.12-rc2
Date: Fri, 4 Oct 2024 17:33:43 -0700	[thread overview]
Message-ID: <202410041733.20AD92E@keescook> (raw)

Hi Linus,

Please pull these hardening fixes for v6.12-rc2.

Thanks!

-Kees

The following changes since commit c121d5cc3a993cdbfab46a152bdd50227a4d5e8c:

  lib/string_choices: Add some comments to make more clear for string choices helpers. (2024-09-05 09:50:16 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 045244dd5d75c61ae37b7b96fe0a95805bd1842d:

  MAINTAINERS: Add security/Kconfig.hardening to hardening section (2024-09-28 13:56:12 -0700)

----------------------------------------------------------------
hardening fixes for v6.12-rc2

- gcc plugins: Avoid Kconfig warnings with randstruct (Nathan Chancellor)

- MAINTAINERS: Add security/Kconfig.hardening to hardening section
  (Nathan Chancellor)

- MAINTAINERS: Add unsafe_memcpy() to the FORTIFY review list

----------------------------------------------------------------
Kees Cook (1):
      MAINTAINERS: Add unsafe_memcpy() to the FORTIFY review list

Nathan Chancellor (2):
      hardening: Adjust dependencies in selection of MODVERSIONS
      MAINTAINERS: Add security/Kconfig.hardening to hardening section

 MAINTAINERS                | 2 ++
 security/Kconfig.hardening | 4 ++--
 2 files changed, 4 insertions(+), 2 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2024-10-05  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-05  0:33 Kees Cook [this message]
2024-10-05 18:07 ` [GIT PULL] hardening fixes for v6.12-rc2 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=202410041733.20AD92E@keescook \
    --to=kees@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.