From: Greg KH <gregkh@linuxfoundation.org>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: ABI mismatch build error for 6.17.y and rustc 1.91.0
Date: Tue, 4 Nov 2025 16:39:30 +0900 [thread overview]
Message-ID: <2025110402-banister-speech-7228@gregkh> (raw)
In-Reply-To: <20a1d4f3-1fa3-4789-aa7d-385d33ea9324@de.bosch.com>
On Tue, Nov 04, 2025 at 08:07:13AM +0100, Dirk Behme wrote:
> On 04/11/2025 06:27, Greg KH wrote:
> > My laptop just upgraded rustc to 1.91.0 and now I get the following
> > build error in 6.17.y when doing a 'allmodconfig' build:
> >
> > RUSTDOC TK rust/kernel/lib.rs
> > error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `kernel`
> > --> rust/kernel/lib.rs:3:1
> > |
> > 3 | //! The `kernel` crate.
> > | ^
> > |
> > = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely
> > = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `core`
> > = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `core`
> > = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error
> >
> > I don't see that on Linus's branch, but maybe I don't have the same
> > build options enabled there. Is 6.17.y missing a patch that is in
> > 6.18-rc to resolve this that I just can't seem to find?
>
> This one
>
> https://github.com/Rust-for-Linux/linux/commit/16c43a56b79e2c3220b043236369a129d508c65a
That is not a valid git id in linux-next :(
> https://lore.kernel.org/rust-for-linux/CANiq72=0JJz5XDHGpiyQBd9AmPCr4veJ=2oJywyyqQB8iMxqvA@mail.gmail.com/
Ok, but why am I not seeing this on 6.18-rc?
thanks,
greg k-h
next prev parent reply other threads:[~2025-11-04 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 5:27 ABI mismatch build error for 6.17.y and rustc 1.91.0 Greg KH
2025-11-04 7:07 ` Dirk Behme
2025-11-04 7:39 ` Greg KH [this message]
2025-11-04 10:39 ` Miguel Ojeda
2025-11-04 14:26 ` Greg KH
2025-11-04 15:10 ` Miguel Ojeda
2025-11-08 5:28 ` Greg KH
2025-11-09 17:31 ` 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=2025110402-banister-speech-7228@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dirk.behme@de.bosch.com \
--cc=rust-for-linux@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