linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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 6/8] mm: rust: add VmAreaNew for f_ops->mmap()
Date: Mon, 20 Jan 2025 14:00:02 +0100	[thread overview]
Message-ID: <87o701d4j1.fsf@kernel.org> (raw)
In-Reply-To: <20250115-vma-v12-6-375099ae017a@google.com> (Alice Ryhl's message of "Wed, 15 Jan 2025 13:35:09 +0000")

"Alice Ryhl" <aliceryhl@google.com> writes:

> This type will be used when setting up a new vma in an f_ops->mmap()
> hook. Using a separate type from VmAreaRef allows us to have a separate
> set of operations that you are only able to use during the mmap() hook.
> For example, the VM_MIXEDMAP flag must not be changed after the initial
> setup that happens during the f_ops->mmap() hook.
>
> To avoid setting invalid flag values, the methods for clearing
> VM_MAYWRITE and similar involve a check of VM_WRITE, and return an error
> if VM_WRITE is set. Trying to use `try_clear_maywrite` without checking
> the return value results in a compilation error because the `Result`
> type is marked #[must_use].
>
> For now, there's only a method for VM_MIXEDMAP and not VM_PFNMAP. When
> we add a VM_PFNMAP method, we will need some way to prevent you from
> setting both VM_MIXEDMAP and VM_PFNMAP on the same vma.
>
> 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




  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
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 [this message]
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=87o701d4j1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox