From: "Danilo Krummrich" <dakr@kernel.org>
To: "Alice Ryhl" <aliceryhl@google.com>
Cc: "Andrey Ryabinin" <ryabinin.a.a@gmail.com>,
"Alexander Potapenko" <glider@google.com>,
"Andrey Konovalov" <andreyknvl@gmail.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH 1/2] rust: kasan: do not pass -Zsanitizer-recover
Date: Wed, 25 Mar 2026 12:06:50 +0100 [thread overview]
Message-ID: <DHBTCP3NHE62.3N96AD6O1L7CK@kernel.org> (raw)
In-Reply-To: <20260325-kasan-rust-sw-tags-v1-1-7d3a765a72aa@google.com>
On Wed Mar 25, 2026 at 10:26 AM CET, Alice Ryhl wrote:
> We do not pass -fsanitize-recover to clang, so for consistency we should
> not pass -Zsanitizer-recover to rustc. Thus, remove these flags.
Isn't this because clang forces it regardless? Is this true for rustc as well?
next prev parent reply other threads:[~2026-03-25 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:26 [PATCH 0/2] rust: add support for Software Tag-Based KASAN Alice Ryhl
2026-03-25 9:26 ` [PATCH 1/2] rust: kasan: do not pass -Zsanitizer-recover Alice Ryhl
2026-03-25 11:06 ` Danilo Krummrich [this message]
2026-03-25 11:47 ` Alice Ryhl
2026-03-25 14:04 ` Danilo Krummrich
2026-03-25 14:30 ` Gary Guo
2026-03-27 11:04 ` Alice Ryhl
2026-03-27 14:28 ` kernel test robot
2026-03-25 9:26 ` [PATCH 2/2] rust: kasan: add support for Software Tag-Based KASAN Alice Ryhl
2026-03-25 11:09 ` Danilo Krummrich
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=DHBTCP3NHE62.3N96AD6O1L7CK@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=andreyknvl@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dvyukov@google.com \
--cc=gary@garyguo.net \
--cc=glider@google.com \
--cc=justinstitt@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=tmgross@umich.edu \
--cc=vincenzo.frascino@arm.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