From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Alice Ryhl <aliceryhl@google.com>, Gary Guo <gary@garyguo.net>,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH 6.12.y] rust: kasan: KASAN+RUST requires clang
Date: Fri, 10 Jul 2026 17:03:05 -0400 [thread overview]
Message-ID: <20260710163023.agent5-0009@kernel.org> (raw)
In-Reply-To: <20260709180359.130168-1-ojeda@kernel.org>
On Thu, Jul 09, 2026 at 08:03:59PM +0200, Miguel Ojeda wrote:
> Kernel KASAN involves passing various llvm/gcc specific arguments to
> the C and Rust compiler. Since these arguments differ between llvm and
> gcc, it's not safe to mix an llvm-based rustc with a gcc build when
> kasan is enabled.
Queued for 6.12, thanks.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-07-10 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 17:36 FAILED: patch "[PATCH] rust: kasan: KASAN+RUST requires clang" failed to apply to 6.12-stable tree gregkh
2026-07-09 18:03 ` [PATCH 6.12.y] rust: kasan: KASAN+RUST requires clang Miguel Ojeda
2026-07-10 21:03 ` Sasha Levin [this message]
2026-07-09 18:05 ` FAILED: patch "[PATCH] rust: kasan: KASAN+RUST requires clang" failed to apply to 6.12-stable tree 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=20260710163023.agent5-0009@kernel.org \
--to=sashal@kernel.org \
--cc=aliceryhl@google.com \
--cc=gary@garyguo.net \
--cc=ojeda@kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox