is_gpt_valid(9)

💖 NAME 💖

okay so we're deep in the Kernel API Manual, and today's main character is is_gpt_valid(9) — it tests one GPT header and PTEs for validity. that's the whole assignment, bestie: one GPT header + PTEs, validity check, slay. ✨

✨ SYNOPSIS ✨

int is_gpt_valid (struct parsed_partitions *state , u64 lba , gpt_header
**gpt , gpt_entry **ptes );

🎀 ARGUMENTS 🎀

• state — the disk's parsed partitions, aka the struct parsed_partitions *state situation. 🫶
• lba — logical block address of the GPT header to test. yep, that exact header. 👑
• gpt — GPT header ptr, filled on return. so it's gpt_header **gpt, and it gets filled when the function comes back. 💅
• ptes — PTEs ptr, filled on return. that's gpt_entry **ptes, also filled on return. 🎀

🦋 DESCRIPTION 🦋

returns 1 if valid, 0 on error. no cap. 🔥

If valid, it returns pointers to newly allocated GPT header and PTEs. that's the win condition, and it's giving "here are your fresh pointers, bestie." 💖

heads up: 1 means valid, 0 means error — don't flip it, iykyk. 😭

🌈 SEE ALSO 🌈

Kernel file ./block/partitions/efi.c is right there in the group chat, and these besties are also linked:

• efi_crc32(9)
• last_lba(9)
• is_pmbr_valid(9)
• read_lba(9)
• alloc_read_gpt_entries(9)
• alloc_read_gpt_header(9)
• is_pte_valid(9)
• compare_gpts(9)
• find_valid_gpt(9)
• utf16_le_to_7bit(9)
• efi_partition(9)

cute sign-off: this page came from ./block/partitions — October 2026 edition — and yes, it ate. 💅✨🎀