linux-kernel - Re: [PATCH v2 0/5] In-place module initialisation

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] [day] [month] [year] [list]

Message-ID: <8de8c3bd-9561-4b54-8bbe-13115bad0800@dakr.org>
Date: Fri, 14 Jun 2024 02:39:09 +0200
From: Danilo Krummrich <me@...r.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
 Wedson Almeida Filho <wedsonaf@...il.com>
Cc: rust-for-linux@...r.kernel.org, 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@...sung.com>, Alice Ryhl
 <aliceryhl@...gle.com>, linux-kernel@...r.kernel.org,
 Wedson Almeida Filho <walmeida@...rosoft.com>
Subject: Re: [PATCH v2 0/5] In-place module initialisation

Hi,

On 4/23/24 02:42, Miguel Ojeda wrote:
> On Thu, Mar 28, 2024 at 8:55 PM Wedson Almeida Filho <wedsonaf@...il.com> wrote:
>>
>> From: Wedson Almeida Filho <walmeida@...rosoft.com>
>>
>> Introduce `InPlaceModule`, which allows modules to be initialised
>> inplace, as opposed to the current state where modules must return an
>> instance which is moved to its final memory location.
>>
>> This allows us to have modules whose state hold objects that must be
>> initialised inplace like locks. It also allows us to implement
>> registrations (e.g., driver registration) inplace and have them similar
>> to their C counterparts where no new allocations are needed.
>>
>> This is built on top of the allocation APIs because the sample module is
>> a modified version of rust_minimal, which would be incompatible with the
>> allocation API series because it uses vectors.
> 
> For the moment, applied 1/5 and 2/5 to `rust-fixes` (tagged for stable
> too) -- thanks everyone!

What's the status of this series? I'd need this for the device / driver patches.

- Danilo

> 
> Cheers,
> Miguel