public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	"Dr. David Alan Gilbert" <linux@treblig.org>,
	Kees Cook <keescook@chromium.org>,
	linux-hardening@vger.kernel.org, llvm@lists.linux.dev
Subject: [GIT PULL] hardening fix for v6.1-rc4
Date: Fri, 4 Nov 2022 09:26:39 -0700	[thread overview]
Message-ID: <202211040926.0E7BBDB1@keescook> (raw)

Hi Linus,

Please pull this tiny kernel hardening fix for v6.1-rc4.

Thanks!

-Kees

The following changes since commit 72c3ebea375c39413d02113758319b74ecd790bd:

  overflow: Refactor test skips for Clang-specific issues (2022-10-25 14:57:42 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.1-rc4

for you to fetch changes up to 6f7630b1b5bc672b54c1285ee6aba752b446672c:

  fortify: Capture __bos() results in const temp vars (2022-10-28 16:07:01 -0700)

----------------------------------------------------------------
kernel hardening fix for v6.1-rc4

- Correctly report struct member size on memcpy overflow (Kees Cook)

----------------------------------------------------------------
Kees Cook (1):
      fortify: Capture __bos() results in const temp vars

 include/linux/fortify-string.h | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2022-11-04 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 16:26 Kees Cook [this message]
2022-11-04 22:46 ` [GIT PULL] hardening fix for v6.1-rc4 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=202211040926.0E7BBDB1@keescook \
    --to=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=llvm@lists.linux.dev \
    --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