From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Gary Guo" <gary@garyguo.net>, "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 1/2] rust: impl_flags: add conversion functions
Date: Tue, 10 Nov 2026 09:11:32 +0100 [thread overview]
Message-ID: <87mrrhqf63.fsf@t14s.mail-host-address-is-not-set> (raw)
In-Reply-To: <DMQSAJDM77O0.Z9EITIPLTKHP@garyguo.net>
"Gary Guo" <gary@garyguo.net> writes:
> On Thu Nov 5, 2026 at 3:42 PM GMT, Andreas Hindborg wrote:
>> Add two conversion functions to the `impl_flags!` macro:
>>
>> - A `From<_>` implementation to convert from the flag value enum to
>> underlying type.
>>
>> - A `TryFrom<_>` implementation to convert from the underlying
>> representation to flag container type.
>>
>> Drop the hand-written `TryFrom<u32> for VmMapFlags` in tyr, which now
>> conflicts with the implementation generated by `impl_flags!`. The two are
>> equivalent.
>>
>> Signed-off-by: Andreas Hindborg <a.hindborg@kernel.org>
>> ---
>> drivers/gpu/drm/tyr/vm.rs | 13 -------------
>> rust/kernel/impl_flags.rs | 31 +++++++++++++++++++++++++++++++
>> 2 files changed, 31 insertions(+), 13 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/tyr/vm.rs b/drivers/gpu/drm/tyr/vm.rs
>> index 1dd11b2b1253..0d6e841a31ed 100644
>> --- a/drivers/gpu/drm/tyr/vm.rs
>> +++ b/drivers/gpu/drm/tyr/vm.rs
>> @@ -141,19 +141,6 @@ fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
>> }
>> }
>>
>> -impl TryFrom<u32> for VmMapFlags {
>> - type Error = Error;
>> -
>> - fn try_from(value: u32) -> Result<Self, Self::Error> {
>> - let valid = VmFlag::Readonly as u32 | VmFlag::Noexec as u32 | VmFlag::Uncached as u32;
>> -
>> - if value & !valid != 0 {
>> - return Err(EINVAL);
>> - }
>> - Ok(Self(value))
>> - }
>> -}
>> -
>> /// Arguments for a virtual memory map operation.
>> struct VmMapArgs<'drm> {
>> /// Access permissions and caching behavior for the mapping.
>> diff --git a/rust/kernel/impl_flags.rs b/rust/kernel/impl_flags.rs
>> index 6051487f6e28..052759b8038d 100644
>> --- a/rust/kernel/impl_flags.rs
>> +++ b/rust/kernel/impl_flags.rs
>> @@ -73,6 +73,17 @@
>> /// // useful for passing the value to a C API.
>> /// let raw: u32 = read_only.bits();
>> /// assert_eq!(raw, Permission::Read as u32);
>> +///
>> +/// // Convert a single flag value to its underlying integer representation.
>> +/// let raw_read: u32 = Permission::Read.into();
>> +/// assert_eq!(raw_read, Permission::Read as u32);
>> +///
>> +/// // Construct a `Permissions` value from a raw integer. `TryFrom` rejects
>> +/// // integers whose set bits do not all correspond to declared flags.
>> +/// let parsed = Permissions::try_from(raw_read | Permission::Write as u32).unwrap();
>> +/// assert!(parsed.contains(Permission::Read));
>> +/// assert!(parsed.contains(Permission::Write));
>> +/// assert!(Permissions::try_from(1 << 7).is_err());
>> /// ```
>> #[macro_export]
>> macro_rules! impl_flags {
>> @@ -115,6 +126,26 @@ fn from(value: $flags) -> Self {
>> }
>> }
>>
>> + impl ::core::convert::From<$flag> for $ty {
>> + #[inline]
>> + fn from(value: $flag) -> Self {
>> + value as Self
>> + }
>> + }
>> +
>> + impl ::core::convert::TryFrom<$ty> for $flags {
>> + type Error = ::kernel::error::Error;
>> +
>> + #[inline]
>> + fn try_from(value: $ty) -> Result<Self, Self::Error> {
>> + if value & !Self::all_bits() != 0 {
>> + return Err(::kernel::error::code::EINVAL);
>
> IMO this should be a new type, perhaps something like
> `kernel::bitflags::UnknownFlags`.
Is really useful? If this happens, you probably cannot recover anyway.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2026-11-10 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 15:42 [PATCH v3 0/2] rust: impl_flags: add convenience functions Andreas Hindborg
2026-11-05 15:42 ` [PATCH v3 1/2] rust: impl_flags: add conversion functions Andreas Hindborg
2026-11-09 15:26 ` Gary Guo
2026-11-10 8:11 ` Andreas Hindborg [this message]
2026-11-05 15:42 ` [PATCH v3 2/2] rust: impl_flags: add bitwise operations with the underlying type 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=87mrrhqf63.fsf@t14s.mail-host-address-is-not-set \
--to=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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
all inboxes | Powered by JetHome®