diff options
| author | Miguel Ojeda <ojeda@kernel.org> | 2024-09-04 16:42:29 +0200 |
|---|---|---|
| committer | Miguel Ojeda <ojeda@kernel.org> | 2024-09-04 23:11:31 +0200 |
| commit | ab309b6e084c70a29f9fa3cee797572bd2340901 (patch) | |
| tree | d0dc23bdee49dd40bc2c40e4204d54991137522f /init | |
| parent | MAINTAINERS: add Trevor Gross as Rust reviewer (diff) | |
| download | linux-ab309b6e084c70a29f9fa3cee797572bd2340901.tar.xz linux-ab309b6e084c70a29f9fa3cee797572bd2340901.zip | |
rust: avoid `box_uninit_write` feature
Like commit 0903b9e2a46c ("rust: alloc: eschew
`Box<MaybeUninit<T>>::write`"), but for the new `rbtree` and `alloc` code.
That is, `feature(new_uninit)` [1] got partially stabilized [2]
for Rust 1.82.0 (expected to be released on 2024-10-17), but it
did not include `Box<MaybeUninit<T>>::write`, which got split into
`feature(box_uninit_write)` [3].
To avoid relying on a new unstable feature, rewrite the `write` +
`assume_init` pair manually.
Link: https://github.com/rust-lang/rust/issues/63291 [1]
Link: https://github.com/rust-lang/rust/pull/129401 [2]
Link: https://github.com/rust-lang/rust/issues/129397 [3]
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Reviewed-by: Matt Gilbride <mattgilbride@google.com>
Link: https://lore.kernel.org/r/20240904144229.18592-1-ojeda@kernel.org
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions