From: Al Viro <viro@zeniv.linux.org.uk>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"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>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] uaccess: rust: use newtype for user pointers
Date: Wed, 28 May 2025 21:01:21 +0100 [thread overview]
Message-ID: <20250528200121.GD2023217@ZenIV> (raw)
In-Reply-To: <20250528174546.GC2023217@ZenIV>
On Wed, May 28, 2025 at 06:45:46PM +0100, Al Viro wrote:
> On Wed, May 28, 2025 at 10:47:12AM +0000, Alice Ryhl wrote:
>
> > We don't currently have any way to perform that kind of pointer-math on
> > user pointers, nor do we have any users of it. I imagine that this type
> > checking is only useful if you can actually perform pointer math in the
> > first place?
>
> What you want is something like
> x->field::UserPtr(beta) iff
> x::UserPtr(alpha) and
> _.field::beta where _::alpha
>
> Generated code would be "add offset and cast to pointer to type of...",
> but doing that manually would really invite headache.
... except that -> comes with wrong connotations, of course. Hell knows
what a decent syntax would look like.
next prev parent reply other threads:[~2025-05-28 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 13:53 [PATCH v2] uaccess: rust: use newtype for user pointers Alice Ryhl
2025-05-27 14:42 ` Greg Kroah-Hartman
2025-05-27 15:20 ` Boqun Feng
2025-05-27 15:22 ` Alice Ryhl
2025-05-27 19:03 ` Christian Schrefl
2025-05-27 19:09 ` Alice Ryhl
2025-05-27 22:12 ` Al Viro
2025-05-27 23:13 ` Boqun Feng
2025-05-28 10:48 ` Alice Ryhl
2025-05-28 15:38 ` Benno Lossin
2025-05-28 16:02 ` Boqun Feng
2025-05-28 10:47 ` Alice Ryhl
2025-05-28 17:45 ` Al Viro
2025-05-28 20:01 ` Al Viro [this message]
2025-05-28 20:35 ` Benno Lossin
2025-05-28 10:52 ` Danilo Krummrich
2025-05-28 16:55 ` Benno Lossin
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=20250528200121.GD2023217@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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