From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Dirk Behme <dirk.behme@de.bosch.com>, 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 23:26:49 +0900 [thread overview]
Message-ID: <2025110413-universe-aerosol-2e83@gregkh> (raw)
In-Reply-To: <CANiq72mENsw=uVUbMFzOor8ZmoeurX+0hiN49fhzBgqMWMM-KQ@mail.gmail.com>
On Tue, Nov 04, 2025 at 11:39:37AM +0100, Miguel Ojeda wrote:
> On Tue, Nov 4, 2025 at 8:43 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > Ok, but why am I not seeing this on 6.18-rc?
>
> It happens in mainline too, so a few possibilities are:
>
> - You have the toolchain forced to an older one (can happen e.g. if
> you are using `rustup` and you have an override on a path, even if the
> default elsewhere is another).
I am using:
make CC=gcc-14 -j32
as my build command line. Hm, that's a mix of gcc and rustc, does that
even work?
> - You are not enabling doctests (KUnit).
CONFIG_KUNIT=y
> - You are not enabling KASAN.
CONFIG_KASAN=y
The full .config can be found here:
https://github.com/gregkh/gregkh-linux/blob/master/stable/configs/6.17.y
The issue only started showing up when I moved rustc from 1.90.0 to
1.91.0, nothing else changed on my system that I can determine.
> Please let me know if you still do not see it, because that it is
> definitely not expected.
I have those options as set above, so this is not expected :)
> I committed the fix yesterday -- it should be in tomorrow's -next.
Cool, what's the git id? I'll be glad to try it.
thanks,
greg k-h
next prev parent reply other threads:[~2025-11-04 14:26 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
2025-11-04 10:39 ` Miguel Ojeda
2025-11-04 14:26 ` Greg KH [this message]
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=2025110413-universe-aerosol-2e83@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dirk.behme@de.bosch.com \
--cc=miguel.ojeda.sandonis@gmail.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