From: Danilo Krummrich <dakr@kernel.org>
To: Tamir Duberstein <tamird@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@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@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] rust: allocator_test: use `posix_memalign`
Date: Thu, 6 Feb 2025 22:56:26 +0100 [thread overview]
Message-ID: <Z6UwCtaO-qVYEN2Z@cassiopeiae> (raw)
In-Reply-To: <20250206-aligned-alloc-v3-1-0cbc0ab0306d@gmail.com>
On Thu, Feb 06, 2025 at 03:49:00PM -0500, Tamir Duberstein wrote:
> The implementation added in commit dd09538fb409 ("rust: alloc: implement
> `Cmalloc` in module allocator_test") used `aligned_malloc` which has
> implementation-defined requirements of its `alignment` parameter.
>
> The macOS implementation of `aligned_alloc` appears to be based on
> `posix_memalign` and inherits the stricter requirements of that
> function, causing test failures on macOS.
>
> Replace `aligned_alloc` with `posix_memalign` and comply with its
> requirements. This ensures uniform behavior across systems.
>
> Fixes: dd09538fb409 ("rust: alloc: implement `Cmalloc` in module allocator_test")
>
> Signed-off-by: Tamir Duberstein <tamird@gmail.com>
Let's wait for clarification before moving on. :)
> ---
> I've intentionally not picked up Danilo's Acked-by from v2 because the
> approach has changed quite a bit.
> ---
> Changes in v3:
> - Replace `aligned_malloc` with `posix_memalign` for portability.
> - Link to v2: https://lore.kernel.org/r/20250202-aligned-alloc-v2-1-5af0b5fdd46f@gmail.com
>
> Changes in v2:
> - Shorten some variable names. (Danilo Krummrich)
> - Replace shadowing alignment variable with a second call to
> Layout::align. (Danilo Krummrich)
> - Link to v1: https://lore.kernel.org/r/20250201-aligned-alloc-v1-1-c99a73f3cbd4@gmail.com
> ---
> rust/kernel/alloc/allocator_test.rs | 27 +++++++++++++++++++++++----
> 1 file changed, 23 insertions(+), 4 deletions(-)
>
> diff --git a/rust/kernel/alloc/allocator_test.rs b/rust/kernel/alloc/allocator_test.rs
> index e3240d16040b..0aa68d955b39 100644
> --- a/rust/kernel/alloc/allocator_test.rs
> +++ b/rust/kernel/alloc/allocator_test.rs
> @@ -23,8 +23,19 @@
> pub type KVmalloc = Kmalloc;
>
> extern "C" {
> - #[link_name = "aligned_alloc"]
> - fn libc_aligned_alloc(align: usize, size: usize) -> *mut crate::ffi::c_void;
> + // NB: `posix_memalign` is intentionally used instead of `aligned_malloc`.
> + //
> + // ISO C (ISO/IEC 9899:2011) defines `aligned_malloc`:
> + //
> + // > The value of alignment shall be a valid alignment supported by the implementation [...].
> + //
> + // POSIX.1-2001 (IEEE 1003.1-2001) defines `posix_memalign`:
> + //
> + // > The value of alignment shall be a power of two multiple of sizeof (void *).
> + //
> + // `posix_memalign` is more portable than (but otherwise identical to) `aligned_malloc`.
> + #[link_name = "posix_memalign"]
> + fn libc_posix_memalign(align: usize, size: usize) -> *mut crate::ffi::c_void;
I don't think this can work. posix_memalign() is defined as follows.
int posix_memalign(void **memptr, size_t alignment, size_t size)
Besides that, I don't think switching to posix_memalign() is desirable, it only
seems to make the code more complicated.
next prev parent reply other threads:[~2025-02-06 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 20:49 [PATCH v3] rust: allocator_test: use `posix_memalign` Tamir Duberstein
2025-02-06 21:56 ` Danilo Krummrich [this message]
2025-02-07 11:43 ` Tamir Duberstein
2025-02-07 12:19 ` Miguel Ojeda
2025-02-07 17:23 ` Tamir Duberstein
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=Z6UwCtaO-qVYEN2Z@cassiopeiae \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--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=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
/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).