linux-kernel - Re: Build break due to merge commit in linux-next 20250916

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] [day] [month] [year] [list]

Message-ID: <b8c4ed52-260d-4963-8d8f-4976229dd4e5@leemhuis.info>
Date: Fri, 19 Sep 2025 07:26:06 +0200
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: Christian Heusel <christian@...sel.eu>, Mark Brown <broonie@...nel.org>
Cc: rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
 regressions@...ts.linux.dev, Bert Karwatzki <spasswolf@....de>
Subject: Re: Build break due to merge commit in linux-next 20250916

CCing Bert, who ran into a similar problem and send a similar patch.

On 16.09.25 16:45, Christian Heusel wrote:
> 
> I have noticed that the recent linux-next release fails to build due to
> a syntax error in the rust code:
> 
>       EXPORTS rust/exports_bindings_generated.h
>       RUSTC L rust/kernel.o
>     error: expected one of `,` or `}`, found `;`
>       --> rust/kernel/block/mq/gen_disk.rs:12:23
>        |
>     12 |     fmt::{self, Write};
>        |                       ^
>        |                       |
>        |                       expected one of `,` or `}`
>        |                       help: missing `,`
> 
>     error: aborting due to 1 previous error
> 
>     make[2]: *** [rust/Makefile:553: rust/kernel.o] Error 1
> 
> It seems like this error was introduced in 6e86e08cdc19 ("Merge branch
> 'rust-next' of https://github.com/Rust-for-Linux/linux.git") and
> introduced with the merge, the attached patch fixes it.

Mark, that error from next-20250916 was gone in next-20250917, but came
back with next-20250918 yesterday. Maybe due to something git rerere had
recorded? But whatever, just wanted to let you know.

Ciao, Thorsten