On Sun, Sep 13, 2026 at 07:52:44PM +0300, Leon Romanovsky wrote: > On Fri, Sep 11, 2026 at 10:41:57PM +0100, Matt Evans wrote: > > Expand the VFIO DMABUF revocation state to three states: > > Not revoked, temporarily revoked, and permanently revoked. > > The thing is that "temporarily revoked" is actually the standard > invalidate_mappings/move_notify mechanism of DMABUF, which wasn't good > for VFIO.
I think temporarily revokes here means it is revoked from a dmabuf perspective Just that VFIO can make it's internal dmabuf work again, there won't be a notification to any importer or an expectation that something like iommufd will re-establish mapping automatically. This is principally a kernel self protection mechanism where the userspace was expected to have removed the dmabuf before issuing a reset/etc. If they didn't then the kernel plonks it and userspace gets a mess to clean up. Jason
