linux-kernel - Re: [PATCH v5 0/3] rust: add `ww

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: <F833F678-85FD-4674-B8A8-9AC9AF0746C1@collabora.com>
Date: Mon, 1 Sep 2025 09:28:53 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Onur Özkan <work@...rozkan.dev>
Cc: Benno Lossin <lossin@...nel.org>,
 Lyude Paul <lyude@...hat.com>,
 linux-kernel@...r.kernel.org,
 rust-for-linux@...r.kernel.org,
 ojeda@...nel.org,
 alex.gaynor@...il.com,
 boqun.feng@...il.com,
 gary@...yguo.net,
 a.hindborg@...nel.org,
 aliceryhl@...gle.com,
 tmgross@...ch.edu,
 dakr@...nel.org,
 peterz@...radead.org,
 mingo@...hat.com,
 will@...nel.org,
 longman@...hat.com,
 felipe_life@...e.com,
 daniel@...lak.dev,
 bjorn3_gh@...tonmail.com
Subject: Re: [PATCH v5 0/3] rust: add `ww_mutex` support

Hi Onur,

> Hi,
> 
> How should the modules be structured? I am thinking something like:
> 
>    rust/kernel/sync/lock/ww_mutex/mod.rs
>    rust/kernel/sync/lock/ww_mutex/core.rs
>    rust/kernel/sync/lock/ww_mutex/ww_exec.rs
> 
> In core, I would include only the essential parts (e.g., wrapper types
> and associated functions) and in ww_exec, I would provide a higher-level
> API similar to drm_exec (more idiomatic rusty version).
> 
> Does this make sense?
> 
> 
> -Onur

That works, but let's not use the name "ww_exec". We don't need the "ww" prefix
given the locking hierarchy. I think it's fine to keep the "exec" nomenclature
for now, but someone else will probably chime in with a better name in the
future.