vmbus_free_buffer(9)

🌸 NAME 🌸

vmbus_free_buffer — release a buffer allocated by vmbus_alloc_buffer(). 💖 Okay so this is the vmbus_free_buffer(9) page from the Kernel API Manual, and we're gonna get you through it, bestie.

✨ SYNOPSIS ✨

void vmbus_free_buffer (void *addr , struct page **chunks , u32 chunk_cnt );

🎀 ARGUMENTS 🎀

• addr — buffer address, or NULL if none was allocated (e.g. cleanup from a failed allocation). literally the “did we even get a buffer?” pointer.
• chunks — chunks array from vmbus_alloc_buffer, or NULL. no cap.
• chunk_cnt — number of entries in chunks. yes bestie, count them.

💅 DESCRIPTION 💅

When chunks is NULL the buffer is a plain vzalloc allocation.

Otherwise tear down the vmap, and for each chunk re-encrypt and free the underlying pages. Any chunk that cannot be re-encrypted is leaked.

⚠️ bestie, real talk: any chunk that cannot be re-encrypted is leaked. That’s the caveat, and it’s giving “handle with care.” 💀

🦋 SEE ALSO 🦋

• Kernel file ./drivers/hv/channel.c
• vmbus_alloc_buffer(9)
• request_arr_init(9)
• vmbus_sendpacket_getid(9)
• vmbus_sendpacket(9)
• __vmbus_recvpacket(9)

okay that’s the whole page, bestie! source/version and date sign-off: from ./drivers/hv, October 2026, and the manual is vmbus_free_buffer(9) — periodt. 💖✨