[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z6UGNbowcvqTN0-T@pollux>
Date: Thu, 6 Feb 2025 19:57:57 +0100
From: Danilo Krummrich <dakr@...nel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Tamir Duberstein <tamird@...il.com>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] rust: alloc: satisfy `aligned_alloc` requirements
On Thu, Feb 06, 2025 at 07:20:20PM +0100, Miguel Ojeda wrote:
> On Thu, Feb 6, 2025 at 7:04 PM Danilo Krummrich <dakr@...nel.org> wrote:
> >
> > I previously checked man posix_memalign(3) and it says:
> >
> > ERRORS
> > EINVAL The alignment argument was not a power of two, or was not a
> > multiple of sizeof(void *).
>
> Yeah, but that may not apply to `alligned_alloc` as far as I can see.
What makes you think so?
AFAICS, the man page applies for posix_memalign, aligned_alloc, memalign,
valloc and pvalloc.
In case behavior differs between the functions, this is stated explicitly, e.g.
in the "RETURN VALUE" section.
The "ERRORS" setion does not differentiate, hence it should apply to all the
functions above, including aligned_alloc.
Do I miss anything?
Powered by blists - more mailing lists