__efivar_entry_get(9)
πΈ 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 π
- Kernel file
./fs/efivarfs/vars.c efivar_init(9)efivar_entry_delete(9)efivar_entry_size(9)efivar_entry_get(9)efivar_entry_set_get_size(9)
source/version: ./fs/efivarfs Β· date: October 2026 β made with π and absolutely zero skipped details, bestie. π¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms