rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
To: "Maíra Canal" <mcanal@igalia.com>,
	"Asahi Lina" <lina@asahilina.net>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@samsung.com>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Matt Gilbride" <mattgilbride@google.com>,
	"Lyude Paul" <lyude@redhat.com>,
	"Danilo Krummrich" <dakr@redhat.com>
Cc: rust-for-linux@vger.kernel.org, kernel-dev@igalia.com,
	"Léo Lanteri Thauvin" <leseulartichaut@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@google.com>
Subject: Re: [PATCH] rust: Add `container_of` and `offset_of` macros
Date: Sun, 18 Feb 2024 14:10:42 -0300	[thread overview]
Message-ID: <1b804b77-d942-4d92-941d-59e72a0b8038@gmail.com> (raw)
In-Reply-To: <20240217153315.56128-1-mcanal@igalia.com>

On 2/17/24 12:32, Maíra Canal wrote:
> From: Asahi Lina <lina@asahilina.net>
> 
> Add Rust counterparts to these C macros. `container_of` is useful for C
> struct subtyping, to recover the original pointer to the container
> structure. `offset_of` is useful for struct-relative addressing.
> 
> Co-authored-by: Miguel Ojeda <ojeda@kernel.org>
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
> Co-authored:by: Léo Lanteri Thauvin <leseulartichaut@gmail.com>
> Signed-off-by: Léo Lanteri Thauvin <leseulartichaut@gmail.com>
> Co-authored-by: Wedson Almeida Filho <wedsonaf@google.com>
> Signed-off-by: Wedson Almeida Filho <wedsonaf@google.com>
> Signed-off-by: Asahi Lina <lina@asahilina.net>
> Signed-off-by: Maíra Canal <mcanal@igalia.com>

A handful of authors? So then, it would be sensible to list their
contributions to the patch, though, it could be done when merged.

> [...]
> +/// Calculates the offset of a field from the beginning of the struct it belongs to.
> +///
> +/// # Examples
> +///
> +/// ```rust
> +/// use kernel::prelude::*;
> +/// use kernel::offset_of;
> +/// struct Test {
> +///     a: u64,
> +///     b: u32,
> +/// }
> +///
> +/// assert_eq!(offset_of!(Test, b), 8);

Would've added a check for field `a`, but that's my personal preference.

> +/// ```
> +#[macro_export]
> +macro_rules! offset_of {
> +    ($type:ty, $($f:tt)*) => {{
> +        let tmp = core::mem::MaybeUninit::<$type>::uninit();
> +        let outer = tmp.as_ptr();
> +        // To avoid warnings when nesting `unsafe` blocks.
> +        #[allow(unused_unsafe)]
> +        // SAFETY: The pointer is valid and aligned, just not initialised; `addr_of` ensures that
> +        // we don't actually read from `outer` (which would be UB) nor create an intermediate
> +        // reference.
> +        let inner = unsafe { core::ptr::addr_of!((*outer).$($f)*) } as *const u8;

Curiously enough, you can get the offset of a member of a field struct
per what `addr_of!` does, i.e. if we have a type `Foo` that contains a
struct field `Bar` which has member `qux`, then
`offset_of!(Foo, bar.qux)` will give out an offset too. I don't know if
this applies for `container_of!`. Just saying.

> [...]

Reviewed-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com>

  reply	other threads:[~2024-02-18 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240217153356eucas1p17c926b49da33a438d286ebb5c1a918c9@eucas1p1.samsung.com>
2024-02-17 15:32 ` [PATCH] rust: Add `container_of` and `offset_of` macros Maíra Canal
2024-02-18 17:10   ` Martin Rodriguez Reboredo [this message]
2024-02-19  9:49   ` Alice Ryhl
2024-02-19 21:57     ` Maíra Canal
2024-02-19 22:04       ` Alice Ryhl
2024-02-20 15:54       ` Miguel Ojeda
2024-02-21 11:27         ` Maíra Canal
2024-02-25 20:30           ` Miguel Ojeda
2024-02-19  9:51   ` Andreas Hindborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1b804b77-d942-4d92-941d-59e72a0b8038@gmail.com \
    --to=yakoyoku@gmail.com \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@redhat.com \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-dev@igalia.com \
    --cc=leseulartichaut@gmail.com \
    --cc=lina@asahilina.net \
    --cc=lyude@redhat.com \
    --cc=mattgilbride@google.com \
    --cc=mcanal@igalia.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=wedsonaf@gmail.com \
    --cc=wedsonaf@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).