dma_buf_attach_revocable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dma_buf_attach_revocable(9) β€” the vibe check for revoke semantics

okay so this is a page from the Kernel API Manual, and bestie, it's a short one but it's important, so stay with me 🫢


✨ NAME ✨

dma_buf_attach_revocable β€” check if a DMA-buf importer implements revoke semantics.

Like, literally just a yes/no vibe check on your importer. That's the whole job. Slay. πŸ’…


🌸 SYNOPSIS 🌸

bool dma_buf_attach_revocable (struct dma_buf_attachment *attach );

Returns a bool, takes one pointer, zero drama. πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • attach β€” the DMA-buf attachment to check πŸ‘€ that's it, that's the whole argument list, she's low maintenance.

πŸ’– DESCRIPTION πŸ’–

So the function returns true if the DMA-buf importer can support the revoke sequence explained in dma_buf_invalidate_mappings within bounded time. Bounded time is the main character here β€” no infinite hangs, no "it'll get there eventually", none of that. ⏳

And what does that actually mean? It means the importer implements invalidate_mappings and ensures that unmap is called as a result. Both things. Not one. Both. No cap. πŸ”₯

fr fr, if your importer can't do the revoke dance in bounded time, this returns something other than true β€” and honestly you should respect it for being honest with you 😭

πŸ‘‘ SEE ALSO πŸ‘‘

Grab a snack, this list is long, but every single one of these is iconic in her own right πŸ“:


and that's the page, bestie πŸ’œ

this icon lives in ./drivers/dma-buf, dated October 2026, and yes, dma_buf_attach_revocable(9) is her full government name πŸŽ€βœ¨ go forth and check your revoke semantics, ily 🫢

πŸ“¦ where this page comes from