From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: a.hindborg@samsung.com, alex.gaynor@gmail.com,
benno.lossin@proton.me, bjorn3_gh@protonmail.com,
boqun.feng@gmail.com, gary@garyguo.net, kees@kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
masahiroy@kernel.org, mmaurer@google.com, nathan@kernel.org,
nicolas@fjasle.eu, ojeda@kernel.org, peterz@infradead.org,
rust-for-linux@vger.kernel.org, samitolvanen@google.com,
wedsonaf@gmail.com
Subject: Re: [PATCH v2b] rust: cfi: add support for CFI_CLANG with Rust
Date: Mon, 16 Sep 2024 16:07:09 +0200 [thread overview]
Message-ID: <CANiq72=B9NmC=1eSaOrg7XutjueQsSXGcBQb7dQFPuL0SFjPsA@mail.gmail.com> (raw)
In-Reply-To: <20240801-kcfi-v2b-2-c93caed3d121@google.com>
On Mon, Aug 19, 2024 at 9:55 AM Alice Ryhl <aliceryhl@google.com> wrote:
>
> +PADDING_RUSTFLAGS := -Zpatchable-function-entry=$(CONFIG_FUNCTION_PADDING_BYTES),$(CONFIG_FUNCTION_PADDING_BYTES)
> +KBUILD_RUSTFLAGS += $(PADDING_RUSTFLAGS)
> +export PADDING_RUSTFLAGS
It is possible to have CALL_PADDING && !FINEIBT, which means one can
trigger a build error if the compiler is not recent enough. Should we
test for CALL_PADDING here?
> + depends on !FINEIBT || RUSTC_VERSION >= 108000
Cheers,
Miguel
next prev parent reply other threads:[~2024-09-16 14:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 13:35 [PATCH v2 0/2] Rust KCFI support Alice Ryhl
2024-08-01 13:35 ` [PATCH v2 1/2] cfi: add CONFIG_CFI_ICALL_NORMALIZE_INTEGERS Alice Ryhl
2024-08-01 13:35 ` [PATCH v2 2/2] rust: cfi: add support for CFI_CLANG with Rust Alice Ryhl
2024-08-19 7:55 ` [PATCH v2b] " Alice Ryhl
2024-09-16 14:07 ` Miguel Ojeda [this message]
2024-09-16 16:14 ` Miguel Ojeda
2024-09-18 17:14 ` Miguel Ojeda
2024-08-01 13:41 ` [PATCH v2 0/2] Rust KCFI support Peter Zijlstra
2024-08-01 20:33 ` Sami Tolvanen
2024-08-06 19:31 ` Kees Cook
2024-08-17 0:13 ` Gatlin Newhouse
2024-09-15 19:09 ` Miguel Ojeda
2024-09-15 19:09 ` Miguel Ojeda
2024-11-26 9:19 ` Peter Zijlstra
2024-11-26 9:37 ` Alice Ryhl
2024-11-26 11:14 ` Peter Zijlstra
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='CANiq72=B9NmC=1eSaOrg7XutjueQsSXGcBQb7dQFPuL0SFjPsA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mmaurer@google.com \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=wedsonaf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).