From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Alice Ryhl" <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Matthew Wilcox" <willy@infradead.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"John Hubbard" <jhubbard@nvidia.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arnd Bergmann" <arnd@arndb.de>, "Jann Horn" <jannh@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v12 2/8] mm: rust: add vm_area_struct methods that require read access
Date: Mon, 20 Jan 2025 13:40:17 +0100 [thread overview]
Message-ID: <875xm9ek0e.fsf@kernel.org> (raw)
In-Reply-To: <20250115-vma-v12-2-375099ae017a@google.com> (Alice Ryhl's message of "Wed, 15 Jan 2025 13:35:05 +0000")
"Alice Ryhl" <aliceryhl@google.com> writes:
> This adds a type called VmAreaRef which is used when referencing a vma
> that you have read access to. Here, read access means that you hold
> either the mmap read lock or the vma read lock (or stronger).
>
> Additionally, a vma_lookup method is added to the mmap read guard, which
> enables you to obtain a &VmAreaRef in safe Rust code.
>
> This patch only provides a way to lock the mmap read lock, but a
> follow-up patch also provides a way to just lock the vma read lock.
>
> Acked-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com> (for mm bits)
> Reviewed-by: Jann Horn <jannh@google.com>
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Reviewed-by: Andreas Hindborg <a.hindborg@kernel.org>
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-01-20 13:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 13:35 [PATCH v12 0/8] Rust support for mm_struct, vm_area_struct, and mmap Alice Ryhl
2025-01-15 13:35 ` [PATCH v12 1/8] mm: rust: add abstraction for struct mm_struct Alice Ryhl
2025-01-20 12:33 ` Andreas Hindborg
2025-01-15 13:35 ` [PATCH v12 2/8] mm: rust: add vm_area_struct methods that require read access Alice Ryhl
2025-01-20 12:40 ` Andreas Hindborg [this message]
2025-01-15 13:35 ` [PATCH v12 3/8] mm: rust: add vm_insert_page Alice Ryhl
2025-01-20 12:47 ` Andreas Hindborg
2025-01-15 13:35 ` [PATCH v12 4/8] mm: rust: add lock_vma_under_rcu Alice Ryhl
2025-01-20 12:50 ` Andreas Hindborg
2025-01-15 13:35 ` [PATCH v12 5/8] mm: rust: add mmput_async support Alice Ryhl
2025-01-15 13:35 ` [PATCH v12 6/8] mm: rust: add VmAreaNew for f_ops->mmap() Alice Ryhl
2025-01-20 13:00 ` Andreas Hindborg
2025-01-15 13:35 ` [PATCH v12 7/8] rust: miscdevice: add mmap support Alice Ryhl
2025-01-17 12:11 ` Greg Kroah-Hartman
2025-01-20 13:48 ` Andreas Hindborg
2025-01-15 13:35 ` [PATCH v12 8/8] task: rust: rework how current is accessed Alice Ryhl
2025-01-20 13:58 ` Andreas Hindborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xm9ek0e.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=surenb@google.com \
--cc=tmgross@umich.edu \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.