linux-kernel - Re: [PATCH v3 3/6] rust: gpuvm: add GpuVm::obtain()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260126163537.0ca199cf@fedora>
Date: Mon, 26 Jan 2026 16:35:37 +0100
From: Boris Brezillon <boris.brezillon@...labora.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Danilo Krummrich <dakr@...nel.org>, Daniel Almeida
 <daniel.almeida@...labora.com>, Janne Grunau <j@...nau.net>, Matthew Brost
 <matthew.brost@...el.com>, Thomas Hellström
 <thomas.hellstrom@...ux.intel.com>, Lyude Paul <lyude@...hat.com>, Asahi
 Lina <lina+kernel@...hilina.net>, dri-devel@...ts.freedesktop.org,
 linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v3 3/6] rust: gpuvm: add GpuVm::obtain()

On Mon, 26 Jan 2026 16:07:30 +0100
Alice Ryhl <aliceryhl@...gle.com> wrote:

> On Mon, Jan 26, 2026 at 4:00 PM Boris Brezillon
> <boris.brezillon@...labora.com> wrote:
> >
> > On Wed, 21 Jan 2026 11:31:19 +0000
> > Alice Ryhl <aliceryhl@...gle.com> wrote:
> >  
> > > +/// A [`GpuVmBo`] object in the GEM list.
> > > +///
> > > +/// # Invariants
> > > +///
> > > +/// Points at a `drm_gpuvm_bo` that contains a valid `T::VmBoData` and is present in the gem list.
> > > +pub struct GpuVmBoResident<T: DriverGpuVm>(NonNull<GpuVmBo<T>>);  
> >
> > I find the name a bit confusing: BO residency is often used to refer to
> > memory backing the buffer object, and in this case, you can end up with
> > a GpuVmBoResident being returned for a BO that has been evicted (one
> > that's no longer resident).  
> 
> Good point. I meant it as "present in list" but I guess there are
> other things a gpuvm may be present in.
> 
> Any naming suggestions?

Valid, Bound, Present, Active?