linux-kernel - Re: [PATCH v4] rust: alloc: satisfy POSIX alignment requirement

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJ-ks9njSCkH2AiC9gx+=+KOp=OYfdz1ph5n_xjVNxH+Lno2CQ@mail.gmail.com>
Date: Tue, 11 Feb 2025 16:50:25 -0500
From: Tamir Duberstein <tamird@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Danilo Krummrich <dakr@...nel.org>, Miguel Ojeda <ojeda@...nel.org>, DJ Delorie <dj@...hat.com>, 
	Eric Blake <eblake@...hat.com>, Will Newton <will.newton@...aro.org>, 
	Paul Eggert <eggert@...ucla.edu>, 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-man@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] rust: alloc: satisfy POSIX alignment requirement

On Tue, Feb 11, 2025 at 4:46 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> On Tue, Feb 11, 2025 at 4:21 PM Tamir Duberstein <tamird@...il.com> wrote:
> >
> > Drat, will do.
>
> Thanks!
>
> > Yep, I mentioned it under "Changes in v4".
>
> I meant to confirm the reasoning -- it is all good, thanks!
> (personally I would probably have dropped it in a case like this,
> since the change in comments is substantial and Danilo was waiting for
> the clarification from Alejandro etc.).
>
> Cheers,
> Miguel

Got it! I've dropped it from v5 in which I've used Gary's pithier
formulation. I'd like to get an acknowledgement that the commit
message and code comment make sense before sending it.

It'd be great to get this into 6.14 so that local builds are clean for
the next cycle.

Cheers.

Tamir