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: <CANiq72mMo9fyw-NbLUQi_5jD68W78Q5ZMn-ubstWCa6hue7qHA@mail.gmail.com>
Date: Sun, 5 Jan 2025 14:33:55 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: open list <linux-kernel@...r.kernel.org>, rust-for-linux@...r.kernel.org, 
	"open list:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@...r.kernel.org>, lkft-triage@...ts.linaro.org, 
	Sasha Levin <sashal@...nel.org>, Anders Roxell <anders.roxell@...aro.org>, 
	Dan Carpenter <dan.carpenter@...aro.org>, Arnd Bergmann <arnd@...db.de>, 
	Miguel Ojeda <ojeda@...nel.org>
Subject: Re: rust/kernel/lib.rs:17:12 : warning: the feature `new_uninit` has
 been stable since 1.82.0 and no longer requires an attribute to enable

On Sun, Jan 5, 2025 at 9:42 AM Naresh Kamboju <naresh.kamboju@...aro.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ