dma_buf_unmap_attachment(9)

💅 dma_buf_unmap_attachment(9) — Kernel API Manual bestie ✨

okay so welcome to the Kernel API Manual page for dma_buf_unmap_attachment(9). This is the unmap + usecount-drop situation, and the whole page is giving cleanup era in the best way. 🫶💖

🌸 NAME 🌸

dma_buf_unmap_attachment — unmaps and decreases usecount of the buffer;might deallocate the scatterlist associated. Is a wrapper for unmap_dma_buf() of dma_buf_ops. 💅

✨ SYNOPSIS ✨

void dma_buf_unmap_attachment (struct dma_buf_attachment *attach ,
struct sg_table *sg_table , enum dma_data_direction direction );

🎀 ARGUMENTS 🎀

• attach — [in] attachment to unmap buffer from 🫶
• sg_table — [in] scatterlist info of the buffer to unmap ✨
• direction — [in] direction of DMA transfer 🦋

💜 DESCRIPTION 💜

This unmaps a DMA mapping for attached obtained by dma_buf_map_attachment.

That's the whole plot, no cap. It's a wrapper for unmap_dma_buf() of dma_buf_ops — yes, the NAME section already spilled that, and we're keeping it. 💅

🌈 SEE ALSO 🌈

Kernel file ./drivers/dma-buf/dma-buf.c, plus the whole iconic crew:

• 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_detach(9)
• dma_buf_pin(9)
• dma_buf_unpin(9)
• dma_buf_map_attachment(9)
• dma_buf_map_attachment_unlocked(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)

okay that's the whole page, bestie. Cute sign-off: source/version is ./drivers/dma-buf, date is October 2026, and the page is dma_buf_unmap_attachment(9). Slay and bye! 💖✨