From: Kees Cook <keescook@chromium.org>
To: samitolvanen@google.com
Cc: Kees Cook <keescook@chromium.org>,
nathan@kernel.org, linux-arm-kernel@lists.infradead.org,
masahiroy@kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, mark.rutland@arm.com,
ndesaulniers@google.com, will@kernel.org,
catalin.marinas@arm.com
Subject: Re: [PATCH v2] cfi: Use __builtin_function_start
Date: Wed, 13 Apr 2022 12:26:33 -0700 [thread overview]
Message-ID: <164987798634.655998.2445977983913600905.b4-ty@chromium.org> (raw)
In-Reply-To: <20220405221618.633743-1-samitolvanen@google.com>
On Tue, 5 Apr 2022 15:16:18 -0700, Sami Tolvanen wrote:
> Clang 14 added support for the __builtin_function_start function,
> which allows us to implement the function_nocfi macro without
> architecture-specific inline assembly and in a way that also works
> with static initializers.
>
> Change CONFIG_CFI_CLANG to depend on Clang >= 14, define
> function_nocfi using __builtin_function_start, and remove the arm64
> inline assembly implementation.
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] cfi: Use __builtin_function_start
https://git.kernel.org/kees/c/e6f3b3c9c109
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: samitolvanen@google.com
Cc: Kees Cook <keescook@chromium.org>,
nathan@kernel.org, linux-arm-kernel@lists.infradead.org,
masahiroy@kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, mark.rutland@arm.com,
ndesaulniers@google.com, will@kernel.org,
catalin.marinas@arm.com
Subject: Re: [PATCH v2] cfi: Use __builtin_function_start
Date: Wed, 13 Apr 2022 12:26:33 -0700 [thread overview]
Message-ID: <164987798634.655998.2445977983913600905.b4-ty@chromium.org> (raw)
In-Reply-To: <20220405221618.633743-1-samitolvanen@google.com>
On Tue, 5 Apr 2022 15:16:18 -0700, Sami Tolvanen wrote:
> Clang 14 added support for the __builtin_function_start function,
> which allows us to implement the function_nocfi macro without
> architecture-specific inline assembly and in a way that also works
> with static initializers.
>
> Change CONFIG_CFI_CLANG to depend on Clang >= 14, define
> function_nocfi using __builtin_function_start, and remove the arm64
> inline assembly implementation.
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] cfi: Use __builtin_function_start
https://git.kernel.org/kees/c/e6f3b3c9c109
--
Kees Cook
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-13 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 22:16 [PATCH v2] cfi: Use __builtin_function_start Sami Tolvanen
2022-04-05 22:16 ` Sami Tolvanen
2022-04-05 22:20 ` Nathan Chancellor
2022-04-05 22:20 ` Nathan Chancellor
2022-04-13 19:26 ` Kees Cook [this message]
2022-04-13 19:26 ` Kees Cook
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=164987798634.655998.2445977983913600905.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.com \
--cc=will@kernel.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.