dma_buf_set_name(9)

📦 version 7.3.1, in nixpkgs unstable

✨ dma_buf_set_name(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for dma_buf_set_name — yes it's a real one, yes it's in the kernel, and yes we're gonna get through it together 💅

🎀 NAME 🎀

dma_buf_set_name — gives a specific dma_buf a name so you can actually track the usage, bestie. Like putting a little sticky note on your iced coffee so nobody at the office drinks it 🥤

And the iconique part? It could also support changing the name of the dma-buf if the same piece of memory is used for multiple purposes between different devices. one memory, many eras, main character energy ✨

🦋 SYNOPSIS 🦋

long dma_buf_set_name (struct dma_buf *dmabuf , const char __user *buf );

🌸 ARGUMENTS 🌸

  • dmabuf [in] — the dmabuf buffer that will be renamed. this is the one getting the glow-up 🫶
  • buf [in] — a piece of userspace memory that contains the name of the dma-buf. like, the name lives over there in userspace and buf is the pointer to it, that's the whole vibe.

💖 DESCRIPTION 💖

Returns 0 on success. slay, we love a 0 🔥

But — and hear me out — if the dma-buf buffer is already attached to devices, it returns -EBUSY. no renaming mid-attachment, periodt. the buffer is booked and busy 💀

🌈 SEE ALSO 🌈

Kernel file ./drivers/dma-buf/dma-buf.c plus the whole friend group 💜:

that's the whole page, no notes 💅 and fr fr, this one came from the ./drivers/dma-buf directory, dated October 2026 — go yell about dma-bufs at your local kernel dev, ily, bye 🧚💫

📦 where this page comes from