dma_buf_detach(9)

🌸 NAME 🌸

okay so this is the dma_buf_detach(9) page from the Kernel API Manual, and it does exactly one iconic job: Remove the given attachment from dmabuf's attachments list. That's the whole vibe. 💅

✨ SYNOPSIS ✨

void dma_buf_detach (struct dma_buf *dmabuf , struct dma_buf_attachment *attach );

🎀 ARGUMENTS 🎀

• dmabuf — [in] buffer to detach from. Like, the buffer we're saying bye to 🫶
• attach — [in] attachment to be detached; is free'd after this call. That's not a drill, bestie: it is free'd after this call 😭

💅 DESCRIPTION 💅

This is the cleanup girlie for a device attachment you got by calling dma_buf_attach. So if dma_buf_attach was the "hey bestie" moment, dma_buf_detach is the graceful exit. ✨

Optionally, this calls dma_buf_ops.detach for device-specific detach. So the generic detach can also do the device-specific one — optional, but very much part of the lore. 🦋

🦋 SEE ALSO 🦋

Kernel file: ./drivers/dma-buf/dma-buf.c

• dma_buf_iter_begin(9)
• dma_buf_iter_next(9)
• implicit fence polling(9)
• dma_buf_set_name(9)
• dma buf device access(9)
• dma_buf_export(9)
• dma_buf_fd(9)
• dma_buf_fd_install(9)
• dma_buf_get(9)
• dma_buf_put(9)
• locking convention(9)
• dma_buf_dynamic_attach(9)
• dma_buf_attach(9)
• dma_buf_pin(9)
• dma_buf_unpin(9)
• dma_buf_map_attachment(9)
• dma_buf_map_attachment_unlocked(9)
• dma_buf_unmap_attachment(9)
• dma_buf_unmap_attachment_unlocked(9)
• dma_buf_attach_revocable(9)
• dma_buf_invalidate_mappings(9)
• cpu access(9)
• dma_buf_begin_cpu_access(9)
• dma_buf_end_cpu_access(9)
• dma_buf_mmap(9)
• dma_buf_vmap(9)
• dma_buf_vmap_unlocked(9)
• dma_buf_vunmap(9)
• dma_buf_vunmap_unlocked(9)

xoxo, source/version ./drivers/dma-buf, October 2026 💖