All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 8 Nov 2025 14:28:20 +0900	[thread overview]
Message-ID: <2025110856-down-hypnotic-8490@gregkh> (raw)
In-Reply-To: <CANiq72nXfq8EJ+-ib044+zGbr2N4hJ_Ygte-4a_dmx4A3S+dng@mail.gmail.com>

On Tue, Nov 04, 2025 at 04:10:29PM +0100, Miguel Ojeda wrote:
> On Tue, Nov 4, 2025 at 3:26 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > Hm, that's a mix of gcc and rustc, does that
> > even work?
> 
> It "works" -- it is a best-effort hack as we always warn, but some
> distributions do use it.
> 
> GCC being used is unrelated to this issue though.
> 
> > The full .config can be found here:
> >         https://github.com/gregkh/gregkh-linux/blob/master/stable/configs/6.17.y
> 
> I picked this one and run it in v6.18-rc4, and I see the issue as expected:
> 
>     git clean -xdf
>     git checkout v6.18-rc4
>     curl -o .config
> https://raw.githubusercontent.com/gregkh/gregkh-linux/refs/heads/master/stable/configs/6.17.y
>     make olddefconfig
>     make
> 
> What is the config where you do not see the issue (after it gets
> sync'd, not before the build), i.e. the one for 6.18 that does not
> fail your build?
> 
> > 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.
> 
> Yes, the issue starts with Rust 1.91.0, so that is expected.
> 
> > Cool, what's the git id?  I'll be glad to try it.
> 
> It is the one from the rust-fixes branch:
> 
>     fad472efab0a805dd939f017c5b8669a786a4bcf
> 
> It is the top one in the rust-fixes branch at either:
> 
>     https://github.com/Rust-for-Linux/linux.git rust-fixes
>     https://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git rust-fixes
> 
> (Dirk gave the parent commit of that one, but in your case you need
> the top one too)

This is now fixed up with the patches tagged for stable, thanks, and
sorry for the noise, I didn't know it was already queued up.

greg k-h

  reply	other threads:[~2025-11-08  5:28 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
2025-11-04 15:10         ` Miguel Ojeda
2025-11-08  5:28           ` Greg KH [this message]
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=2025110856-down-hypnotic-8490@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.