applied: [pbs-devel] [PATCH proxmox] lang: Remove offsetof macro

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

On Mon, 26 Jan 2026 15:12:11 +0100, Maximiliano Sandoval wrote:
> With rust 1.90 this will crash while running cargo test with
> 
> $ RUST_BACKTRACE=1 cargo test
> 
> null pointer dereference occurred
> stack backtrace:
>    0: __rustc::rust_begin_unwind
>              at /usr/src/rustc-1.90.0/library/std/src/panicking.rs:697:5
>    1: core::panicking::panic_nounwind_fmt::runtime
>              at /usr/src/rustc-1.90.0/library/core/src/panicking.rs:117:22
>    2: core::panicking::panic_nounwind_fmt
>              at /usr/src/rustc-1.90.0/library/core/src/intrinsics/mod.rs:2367:9
>    3: core::panicking::panic_null_pointer_dereference
>              at /usr/src/rustc-1.90.0/library/core/src/panicking.rs:311:5
>    4: rust_out::main::_doctest_main_proxmox_lang_src_lib_rs_71_0
>    5: rust_out::main
>    6: core::ops::function::FnOnce::call_once
> 
> [...]

Applied, thanks!
Note that I rewrote the commit message completely, as having a full ordinary
rust backtrace with 90% being just the standard panic and unwind frame pointers
is really not providing anything useful, OTOH., knowing that there is a
built-in offset_of macro since rust 1.77, that there is no usage of our macro
in our code anymore, and having some references to this lint changing from a
warning to an error provides context and background that is good to know.

[1/1] lang: Remove offsetof macro
      commit: 2c70b4c98a6f6c86755f97bae109bacd3c3b1703