dma_resv_locking_ctx(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dma_resv_locking_ctx(9) — a Kernel API Manual moment

okay so bestie, welcome to the dma_resv_locking_ctx page, straight out of the Kernel API Manual ✨ this one's short but it's iconic in a deeply unhinged way, trust.

✨ NAME ✨

dma_resv_locking_ctx — returns the context used to lock the object 🎀

🦋 SYNOPSIS 🦋

struct ww_acquire_ctx * dma_resv_locking_ctx (struct dma_resv *obj );

🌸 ARGUMENTS 🌸

  • obj — the reservation object. that's it. that's the whole argument. she's low maintenance 💅

🔥 DESCRIPTION 🔥

So what does it actually do? It returns the context used to lock a reservation object, or NULL if no context was used or if the object is not locked at all. two very different reasons, same NULL, no cap 🙈

⚠️ WARNING: this interface is pretty horrible, but TTM needs it because it doesn't pass the struct ww_acquire_ctx around in some very long callchains. Everyone else just uses it to check whether they're holding a reservation or not.

like, the manpage itself is calling it horrible 😭 we love a self-aware API. TTM's out here raw-dogging long callchains without passing the struct around, so this exists to save it — and everybody else is just using it as a vibe check: am i holding a reservation or not bestie? ✨

💜 SEE ALSO 💜

Kernel file ./include/linux/dma-resv.h, plus the whole squad:

okay that's the whole page, you ate that 🫶 this lil gem lives in ./include/linux, dropped October 2026, in the Kernel API Manual — go forth and check your locks, bestie, and remember: NULL doesn't always mean unlocked, sometimes it just means nobody passed the context 💀💖

📦 where this page comes from