linux-kernel - Re: linux-next: build failure in the final build

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72n=h5dzcmNULoXSZ4h2133hSY-AtU-xGxeJ=hfmgY1XZw@mail.gmail.com>
Date: Wed, 21 Jan 2026 20:24:07 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Mark Brown <broonie@...nel.org>, Danilo Krummrich <dakr@...nel.org>, 
	Beata Michalska <beata.michalska@....com>, Carsten Haitzler <carsten.haitzler@...s.arm.com>, 
	Rob Herring <robh@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure in the final build

On Wed, Jan 21, 2026 at 8:14 PM Alice Ryhl <aliceryhl@...gle.com> wrote:
>
> Hrm I saw you had this last time too. I'm not sure how you're triggering
> it - I haven't run into it myself and I do enable warnings. But I'll try
> to repro and fix it.
>
> Note that for this kind of thing you can add `#![allow(warnings)]` to
> the top of a file to silence warnings.

Mark: we are in a call right now and Danilo asked about this -- I have
a similar issue with CI with `bounded.rs` in 1.80.0, so Danilo tested
1.80.0 and 1.80.1 and indeed 1.80.0 is broken.

We are upping the minimum to 1.85.0 soon, so it is not a big deal.

Could you please upgrade to Rust 1.80.1 at least for linux-next runs?
Where are you taking the toolchain from? i.e. I would expect a distro
to provide the fixed .1

We hope that helps!

Cheers,
Miguel