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,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Kees Cook" <kees@kernel.org>,
	"Nilay Shroff" <nilay@linux.ibm.com>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"Yury Norov" <yury.norov@gmail.com>
Subject: [GIT PULL] hardening fix for v6.13-rc4
Date: Mon, 16 Dec 2024 16:34:51 -0800	[thread overview]
Message-ID: <202412161633.8F8CF08C@keescook> (raw)

Hi Linus,

Please pull this hardening fix for v6.13-rc4. Silences a GCC value-range
warning that is being ironically triggered by bounds checking.

Thanks!

-Kees

The following changes since commit f06e108a3dc53c0f5234d18de0bd224753db5019:

  Compiler Attributes: disable __counted_by for clang < 19.1.3 (2024-11-19 08:48:27 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 239d87327dcd361b0098038995f8908f3296864f:

  fortify: Hide run-time copy size from value range tracking (2024-12-16 16:23:07 -0800)

----------------------------------------------------------------
hardening fix for v6.13-rc4

- FORTIFY: Silence GCC value range warnings due to warning-only bounds checks

----------------------------------------------------------------
Kees Cook (1):
      fortify: Hide run-time copy size from value range tracking

 include/linux/fortify-string.h | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

-- 
Kees Cook

             reply	other threads:[~2024-12-17  0:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  0:34 Kees Cook [this message]
2024-12-17 17:25 ` [GIT PULL] hardening fix for v6.13-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=202412161633.8F8CF08C@keescook \
    --to=kees@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=nilay@linux.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yury.norov@gmail.com \
    /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.