From: Andreas Hindborg <a.hindborg@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Lorenzo Stoakes" <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
"Boqun Feng" <boqun@kernel.org>,
linux-mm@kvack.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] rust: page: add `SafePage` for race-free page access
Date: Wed, 10 Jun 2026 10:48:53 +0200 [thread overview]
Message-ID: <87a4t2hjbe.fsf@kernel.org> (raw)
In-Reply-To: <aikJoacZW5JMEx74@google.com>
"Alice Ryhl" <aliceryhl@google.com> writes:
> On Fri, Jun 05, 2026 at 02:49:14PM +0200, Andreas Hindborg wrote:
>> `SafePage` wraps a regular page but adds an invariant that the page data
>> area does not incur data races. This means `SafePage` cannot be mapped to
>> user space or shared with devices, and it becomes simpler to directly
>> reference the contents of the page.
>>
>> Signed-off-by: Andreas Hindborg <a.hindborg@kernel.org>
>
> Perhaps it should be called ExclusivePage?
Yes, let's do that.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2026-06-10 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 12:49 [PATCH v2 0/2] rust: pages that cannot be racy Andreas Hindborg
2026-06-05 12:49 ` [PATCH v2 1/2] rust: page: add `SafePage` for race-free page access Andreas Hindborg
2026-06-10 6:52 ` Alice Ryhl
2026-06-10 8:48 ` Andreas Hindborg [this message]
2026-06-10 7:24 ` Miguel Ojeda
2026-06-10 8:46 ` Andreas Hindborg
2026-06-05 12:49 ` [PATCH v2 2/2] rust: page: add method to copy data between safe pages 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=87a4t2hjbe.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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