dma_fence_get(9)

💖 dma_fence_get(9) 💖

okay so we're in the Kernel API Manual today bestie, and this is the page for dma_fence_get — the little function that's literally just "yes, keep this fence alive please" 🎀

---

✨ NAME ✨

dma_fence_get — increases refcount of the fence 🔥

---

🌸 SYNOPSIS 🌸

struct dma_fence * dma_fence_get (struct dma_fence *fence );

---

🦋 ARGUMENTS 🦋

• fence — the fence whose refcount you're bumping up. that's it, that's the whole argument 💅

---

💜 DESCRIPTION 💜

Returns the same fence, with refcount increased by 1. that's genuinely the entire lore. it hands you back the exact same fence you passed in, just with one more ref on it. no cap, that's the whole function 🫶✨

---

👑 SEE ALSO 👑

Kernel file ./include/linux/dma-fence.h 🌈 and like, a whole friend group of related pages:

• struct dma_fence(9)
• struct dma_fence_cb(9)
• struct dma_fence_ops(9)
• dma_fence_was_initialized(9)
• dma_fence_put(9)
• dma_fence_get_rcu(9)
• dma_fence_get_rcu_safe(9)
• dma_fence_spinlock(9)
• dma_fence_lock_irqsave(9)
• dma_fence_unlock_irqrestore(9)
• dma_fence_assert_held(9)
• Safe external access to driver provided object members(9)
• dma_fence_is_signaled_locked(9)
• dma_fence_is_signaled(9)
• __dma_fence_is_later(9)
• dma_fence_is_later(9)
• dma_fence_is_later_or_same(9)
• dma_fence_later(9)
• dma_fence_get_status_locked(9)
• dma_fence_set_error(9)
• dma_fence_timestamp(9)
• dma_fence_wait(9)
• dma_fence_is_array(9)
• dma_fence_is_chain(9)
• dma_fence_is_container(9)

---

ngl bestie, if you take a ref with dma_fence_get you gotta give it back with dma_fence_put — that's the vibe check that keeps the kernel from leaking. don't leave it on read 💀

---

anyway that's the page!! brought to you from ./include/linux, dated October 2026, in the Kernel API Manual — mwah, go forth and refcount responsibly 🧚💖⭐