rust-lang
Wrap padding fields in `Padding(MaybeUninit<T>)`
libc uses integers and aggregates of integers for explicit padding byte fields. When these fields are returned from C, they might be uninitialized. We currently do not have any wording in the spec saying that an uninitialized integer is not instant undefined behavior, and there are proposals that define them to both be ok, and to actually be instant undefined behavior.
These padding fields should use MaybeUninit<INT> instead.
The right way to actually fix this issue is to actually remove these padding fields. They only exist because repr(align(N)), repr(packed(N)), unions, etc. did not exist when these types were added. For toolchains that actually support MaybeUninit, we can actually do better and don't use any kind of padding fields at all. For toolchains that do not support repr(align(N)), repr(packed(N)), unions, etc. MaybeUninit does not exist and cannot be actually implemented in Rust, so there is nothing we can do.
For C types using FAM, there is no way to avoid undefined behavior in Rust today, so we have to use explicit padding fields.
Removing these fields or changing their type are major breaking changes when these fields are public. Most of these fields are private, but some of them aren't.
Rust currently does not exploit this potential undefined behavior for anything, and for most targets, it cannot actually exploit it since the C library is dynamically linked or linked without cross-lang-lto. If we start using cross-lang-lto, e.g., when statically-linking musl, this could become an issue in the future.
cc @emilio - I think rust-bindgen probably has the same issues when it comes to automatically-generated explicit padding fields. The constraints of fixing that there are probably the same as the constraints of fixing that here: where MaybeUninit is available, one can probably do better and not emit padding fields in the first place, and where MaybeUninit is not available, there might not be a way to avoid the UB anyways (e.g. depending on how old the Rust version being targeted is). For FAMs, I don't think rust-bindgen can do anything either.
Yes, that's right. I've opened https://github.com/rust-lang/rust-bindgen/issues/1606 to track this.
I don’t believe that this is likely to cause problems in practice: C code in system libraries is not visible to the Rust compiler, so rustc has no way to know that these fields are uninitialized. bindgen has a bigger problem because it may be used with LTO.
C code in system libraries is not visible to the Rust compiler, so rustc has no way to know that these fields are uninitialized.
Actually, that's not true with linker-plugin-lto.
Discussed at #t-libs > Questions and polls about `libc` 1.0 @ 💬, we probably actually want a struct Padding<T>(MaybeUninit<T>) that we implement Default for.
