On Sun, Jan 5, 2025 at 9:42 AM Naresh Kamboju naresh.kamboju@linaro.org wrote:

The following kselftest rust builds failed on sashal/linus-next.git due to following build warnings / errors.

Good: 829d8581c398a96deea1d6bc78578950347dcbec Bad: b2d472701a703596889c3fd067fd8929aeffc4be

These seem unrelated, old but rebased/recommitted recently (without SoB).

warning: the feature `new_uninit` has been stable since 1.82.0 and no longer requires an attribute to enable --> /rust/kernel/lib.rs:17:12 | 17 | #![feature(new_uninit)] | ^^^^^^^^^^ | = note: `#[warn(stable_features)]` on by default

This should not happen since commit 8e95e53ca379 ("rust: allow `stable_features` lint"), which is in v6.11-rc7.

error[E0658]: use of unstable library feature 'box_uninit_write' --> /rust/kernel/alloc/box_ext.rs:41:12 | 41 | Ok(Box::write(b, x)) | ^^^^^^^^^^ | = note: see issue #129397 https://github.com/rust-lang/rust/issues/129397 for more information = help: add `#![feature(box_uninit_write)]` to the crate attributes to enable = note: this compiler was built on 2024-11-26; consider upgrading it if it is out of date

This should not happen since commit 0903b9e2a46c ("rust: alloc: eschew `Box<MaybeUninit<T>>::write`"), which is also in v6.11-rc7. (The file is gone nowadays too, since v6.13-rc1).

toolchain: rustgcc compiler: 'name': 'gcc', 'version': '14', 'version_full': 'gcc (Debian 14.2.0-8) 14.2.0'

By the way, it would be nice to mention here the Rust compiler too, if used.

Thanks for the report! I think there is nothing to be done here given the details above.

Cheers, Miguel

I'm sorry, this is my bad: I haven't realized anyone else will be looking at these results...

Naresh, I'm cheating and using this tree to bisect the issue you've originally reported in https://lore.kernel.org/all/CA+G9fYvcBvbabg+m7brKfpGCGZUcK+KHHTFX7hFvW6GmN2X... .

It seems we can't get traction to get it fixes, so I'm trying to make forward progress.

Please ignore linus-next for the next day or two :)