__efivar_entry_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, this is the manual page for __efivar_entry_get(9) from the Kernel API Manual, and it's literally the page for __efivar_entry_get. The short version is right there in the name: it calls get_variable(). That's the vibe. ✨

πŸŽ€ SYNOPSIS πŸŽ€

int __efivar_entry_get (struct efivar_entry *entry , u32 *attributes ,
       unsigned long *size , void *data );

πŸ’– ARGUMENTS πŸ’–

  • entry β€” read data for this variable. That's your efivar entry, bestie. 🫢
  • attributes β€” variable attributes. Yes, those attributes. πŸ’…
  • size β€” size of data buffer. Gotta know how big the buffer is, no cap.
  • data β€” buffer to store variable data. This is where the data goes. πŸŽ€

πŸ¦‹ DESCRIPTION πŸ¦‹

no cap, there is one giant MUST here: the caller MUST call efivar_entry_iter_begin and efivar_entry_iter_end before and after the invocation of this function, respectively. periodt. 🫢

So yeah: efivar_entry_iter_begin goes before, and efivar_entry_iter_end goes after β€” respect the order, bestie. It's giving "bookends but make it kernel code." πŸ’…

🌈 SEE ALSO 🌈


source/version: ./fs/efivarfs Β· date: October 2026 β€” made with πŸ’– and absolutely zero skipped details, bestie. πŸ¦‹

πŸ“¦ where this page comes from