From: Kees Cook <kees@kernel.org>
To: Jan Hendrik Farr <kernel@jfarr.cc>
Cc: Kees Cook <kees@kernel.org>,
nathan@kernel.org, ojeda@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com,
thorsten.blum@toblux.com, ardb@kernel.org, oliver.sang@intel.com,
gustavoars@kernel.org, kent.overstreet@linux.dev, arnd@arndb.de,
gregkh@linuxfoundation.org, akpm@linux-foundation.org,
tavianator@tavianator.com, linux-hardening@vger.kernel.org,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/1] Compiler Attributes: disable __counted_by for clang < 19.1.3
Date: Tue, 19 Nov 2024 09:26:27 -0800 [thread overview]
Message-ID: <173203718634.3118906.4631874727014346327.b4-ty@kernel.org> (raw)
In-Reply-To: <20241029140036.577804-2-kernel@jfarr.cc>
On Tue, 29 Oct 2024 15:00:36 +0100, Jan Hendrik Farr wrote:
> This patch disables __counted_by for clang versions < 19.1.3 because
> of the two issues listed below. It does this by introducing
> CONFIG_CC_HAS_COUNTED_BY.
>
> 1. clang < 19.1.2 has a bug that can lead to __bdos returning 0:
> https://github.com/llvm/llvm-project/pull/110497
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] Compiler Attributes: disable __counted_by for clang < 19.1.3
https://git.kernel.org/kees/c/f06e108a3dc5
Take care,
--
Kees Cook
next prev parent reply other threads:[~2024-11-19 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 14:00 [PATCH 0/1] " Jan Hendrik Farr
2024-10-29 14:00 ` [PATCH 1/1] Compiler Attributes: " Jan Hendrik Farr
2024-10-29 15:10 ` Thorsten Blum
2024-11-19 17:26 ` Kees Cook [this message]
2025-06-09 13:14 ` Dafna Hirschfeld
2025-06-09 13:51 ` Miguel Ojeda
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=173203718634.3118906.4631874727014346327.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=justinstitt@google.com \
--cc=kent.overstreet@linux.dev \
--cc=kernel@jfarr.cc \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=oliver.sang@intel.com \
--cc=stable@vger.kernel.org \
--cc=tavianator@tavianator.com \
--cc=thorsten.blum@toblux.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 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®