[PATCH 0/3] Memory management patches needed by Rust Binder
From: Alice Ryhl
Date: Wed Jan 24 2024 - 06:21:27 EST
This patchset contains some abstractions needed by the Rust
implementation of the Binder driver for passing data between userspace,
kernelspace, and directly into other processes.
These abstractions do not exactly match what was included in the Rust
Binder RFC - I have made various improvements and simplifications since
then. Nonetheless, please see the Rust Binder RFC [1] to get an
understanding for how this will be used:
Users of "rust: add userspace pointers"
and "rust: add typed accessors for userspace pointers":
rust_binder: add binderfs support to Rust binder
rust_binder: add threading support
rust_binder: add nodes and context managers
rust_binder: add oneway transactions
rust_binder: add death notifications
rust_binder: send nodes in transactions
rust_binder: add BINDER_TYPE_PTR support
rust_binder: add BINDER_TYPE_FDA support
rust_binder: add process freezing
Users of "rust: add abstraction for `struct page`":
rust_binder: add oneway transactions
rust_binder: add vma shrinker
Especially the second patch with typed accessors needs review. It
contains a Rust analogy for when the C-side skips `check_object_size`,
and I would be very happy to receive feedback about whether I am going
about this in a reasonable way.
Links: https://lore.kernel.org/rust-for-linux/20231101-rust-binder-v1-0-08ba9197f637@xxxxxxxxxx/ [1]
Signed-off-by: Alice Ryhl <aliceryhl@xxxxxxxxxx>
---
Alice Ryhl (2):
rust: add typed accessors for userspace pointers
rust: add abstraction for `struct page`
Wedson Almeida Filho (1):
rust: add userspace pointers
rust/bindings/bindings_helper.h | 1 +
rust/helpers.c | 68 ++++++++
rust/kernel/lib.rs | 2 +
rust/kernel/page.rs | 176 ++++++++++++++++++++
rust/kernel/user_ptr.rs | 347 ++++++++++++++++++++++++++++++++++++++++
5 files changed, 594 insertions(+)
---
base-commit: 6613476e225e090cc9aad49be7fa504e290dd33d
change-id: 20231128-alice-mm-bc533456cee8
Best regards,
--
Alice Ryhl <aliceryhl@xxxxxxxxxx>