dma_fence_get_stub(9)

💖 NAME 💖

Okay bestie, welcome to dma_fence_get_stub(9) from the Kernel API Manual. The whole vibe is right there in the name: dma_fence_get_stub — return a signaled fence. That’s the mission, iconic behavior only. ✨

✨ SYNOPSIS ✨

struct dma_fence * dma_fence_get_stub (void );

🫶 ARGUMENTS 🫶

• void — no arguments. Literally zero, bestie. Not a single parameter. The function said “I need nothing” and honestly? main character energy. 💅

🌸 DESCRIPTION 🌸

This returns a stub fence which is already signaled. Periodt — that’s the whole point of the stub, no cap.

The fence’s timestamp corresponds to the initialisation time of the linux kernel. That’s the timestamp detail, fr fr: kernel initialisation time. 🕰️✨

🦋 SEE ALSO 🦋

Kernel file: ./drivers/dma-buf/dma-fence.c — the source file, bestie, go look if you want the full lore. The rest of the friend group:

• DMA fences overview(9)
• fence cross-driver contract(9)
• dma_fence_allocate_private_stub(9)
• dma_fence_context_alloc(9)
• fence signalling annotation(9)
• dma_fence_begin_signalling(9)
• dma_fence_end_signalling(9)
• dma_fence_signal_timestamp_locked(9)
• dma_fence_signal_timestamp(9)
• dma_fence_signal_locked(9)
• dma_fence_check_and_signal_locked(9)
• dma_fence_check_and_signal(9)
• dma_fence_signal(9)
• dma_fence_wait_timeout(9)
• dma_fence_release(9)
• dma_fence_free(9)
• dma_fence_enable_signaling(9)
• dma_fence_add_callback(9)
• dma_fence_get_status(9)
• dma_fence_remove_callback(9)
• dma_fence_default_wait(9)
• dma_fence_wait_any_timeout(9)
• deadline hints(9)
• dma_fence_set_deadline(9)
• dma_fence_describe(9)
• dma_fence_init(9)
• dma_fence_init64(9)
• dma_fence_driver_name(9)
• dma_fence_timeline_name(9)

Cute lil sign-off: this page lives under the source path ./drivers/dma-buf, is dated October 2026, and answers to dma_fence_get_stub(9) through and through. Bye bestie — slay, stay signaled, mwah 💋✨