dma_fence_remove_callback(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dma_fence_remove_callback — the kernel API manual, bestie edition ✨

okay so this is the page for dma_fence_remove_callback(9) — it lives in the Kernel API Manual and it's all about ✨un-queueing✨ a callback, no cap.

🎀 NAME 🎀

dma_fence_remove_callback — remove a callback from the signaling list. literally that's it, that's the whole gig 🫶

🦋 SYNOPSIS 🦋

bool dma_fence_remove_callback (struct dma_fence *fence , struct
dma_fence_cb *cb );

it returns a bool, bestie — remember that, it matters later 👀

🌸 ARGUMENTS 🌸

  • fence — the fence to wait on 🚧
  • cb — the callback to remove 🗑️

💖 DESCRIPTION 💖

so what this does: it removes a callback that you previously queued up from the fence. that's the vibe. 🌈

it returns true if the callback is successfully removed, or false if the fence has already been signaled. two outcomes, no in-between, periodt. ✨

⚠️ WARNING ⚠️: cancelling a callback should only be done if you really know what you're doing, because deadlocks and race conditions could occur all too easily. not me stressing 😭 for this reason, it should only ever be done on hardware lockup recovery, with a reference held to the fence. that's the rule, iykyk 💅

also: behaviour is undefined if cb has not been added to fence using dma_fence_add_callback beforehand. undefined behaviour is not cute, bestie, please don't 🙈

👑 SEE ALSO 👑

pretty sure you'll wanna peek at these too, fr fr:

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

and that's the whole page, bestie!! 🧚💜 this one's sourced from ./drivers/dma-buf, dated October 2026, and yeah — the title dma_fence_remove_callback(9) is right there at the top and the bottom of the original, we been knew 💅 slay, go cancel some callbacks responsibly (or don't, see the warning above 😭) 🍓⭐🔥

📦 where this page comes from