efi_free_all_buff_pages(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… efi_free_all_buff_pages(9) β€” Kernel API Manual ✨

okay so bestie, welcome to the <pink>Kernel API Manual</pink> entry for efi_free_all_buff_pages β€” yes the whole name, it's long, we cope 🫢 this one's short and sweet and honestly kind of a baddie. let's get into it.


🌸 NAME 🌸

efi_free_all_buff_pages β€” frees, like, all the buffer pages that were allocated before. not some. all. it's giving cleanup era 🧹✨


πŸŽ€ SYNOPSIS πŸŽ€

void efi_free_all_buff_pages (struct capsule_info *cap_info );

that's it. that's the whole signature. returns void, takes one pointer, no notes πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • cap_info β€” a pointer to the current instance of the capsule_info structure. yeah, the one you're working with right now. hand it over and it knows what's up 🫢

πŸ’– DESCRIPTION πŸ’–

so here's the tea: this function frees the buffer pages, yes β€” but that's not all it does, and honestly the second part is the main character πŸ‘‘

it also flags NO_FURTHER_WRITE_ACTION πŸ”₯ which makes it cease processing data in any subsequent write(2) calls. like, it's done. the vibe check failed. no more writing.

and when does that lift? only when close(2) is called. so the whole thing is locked down from the flag until close β€” no in-between, no sneaky extra writes, periodt πŸ’€

lowkey important: once NO_FURTHER_WRITE_ACTION is set, those write(2) calls just stop being processed. it's not a suggestion, it's a boundary. βœ‹

⭐ SEE ALSO ⭐

it's giving friend group. go read them all, iykyk 🌈


mwah πŸ’‹ that's the page! sourced from ./drivers/firmware/efi, dated October 2026, filed under <lavender>Kernel API Manual</lavender> β€” go forth and free those buffer pages responsibly bestie πŸ‘‘βœ¨

πŸ“¦ where this page comes from