[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230531145939.3714886-1-aliceryhl@google.com>
Date: Wed, 31 May 2023 14:59:35 +0000
From: Alice Ryhl <aliceryhl@...gle.com>
To: rust-for-linux@...r.kernel.org
Cc: Miguel Ojeda <ojeda@...nel.org>,
Wedson Almeida Filho <wedsonaf@...il.com>,
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>,
Alice Ryhl <aliceryhl@...gle.com>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
linux-kernel@...r.kernel.org, patches@...ts.linux.dev
Subject: [PATCH v3 0/4] Update thread safety markers
In Rust, the `Send` and `Sync` traits are used to mark in what ways a
specific type is thread safe. In this patch series, I add some missing
thread safety markers and improve the documentation related to them.
This change will let you compile some code that would currently fail to
compile even though it doesn't actually violate any thread safety rules.
You can find a definition of what these marker traits mean at [1].
Changes since v2:
* Removed "for example" as suggested in [2].
* Added Reviewed-by annotations from v2 review.
[1]: https://stackoverflow.com/a/68708557/1704411
[2]: https://lore.kernel.org/all/20230523165027.71600b4b.gary@garyguo.net/
Alice Ryhl (4):
rust: sync: reword the `Arc` safety comment for `Send`
rust: sync: reword the `Arc` safety comment for `Sync`
rust: specify when `ARef` is thread safe
rust: task: add `Send` marker to `Task`
rust/kernel/sync/arc.rs | 12 +++++++-----
rust/kernel/task.rs | 10 ++++++++--
rust/kernel/types.rs | 13 +++++++++++++
3 files changed, 28 insertions(+), 7 deletions(-)
base-commit: ac9a78681b921877518763ba0e89202254349d1b
--
2.41.0.rc0.172.g3f132b7071-goog
Powered by blists - more mailing lists