sync_file_get_name(9)

💖 sync_file_get_name(9) 💖

okay bestie, welcome to the Kernel API Manual page for sync_file_get_name(9) — we folded the manual name right into the intro so nobody has to read a boring header line, periodt ✨

🌸 NAME 🌸

sync_file_get_name — get the name of the sync_file 🎀

🦋 SYNOPSIS 🦋

char * sync_file_get_name (struct sync_file *sync_file , char *buf , int len );

✨ ARGUMENTS ✨

• sync_file — the sync_file to get the fence from, bestie 🫶
• buf — destination buffer to copy the sync_file name into, slay 💅
• len — available size of the destination buffer, fr fr 🌸

💜 DESCRIPTION 💜

so every sync_file may have a name assigned either by the user (when merging sync_files together) or created from the fence it contains. in that latter case, construction of the name is deferred until use — and so it requires sync_file_get_name. no cap, that's the whole vibe, and the deferring is literally the reason this function exists 😭✨

🌈 RETURN 🌈

a string representing the name — iconic behavior, honestly 👑💖

🎀 SEE ALSO 🎀

• Kernel file ./drivers/dma-buf/sync_file.c 🦋
• sync_file_create(9) ⭐
• sync_file_get_fence(9) 🍓
• sync_file_merge(9) 💫

okay that's the page, bestie — this one comes from the Kernel API Manual, with its source/version under ./drivers/dma-buf and dated October 2026. mwah, go forth and name those sync_files 💖💅