firmware_ma...ntry_in_list(9)

✨ firmware_map_find_entry_in_list — Kernel API Manual ✨

ok so bestie, welcome to the Kernel API Manual 💖 this little page is all about firmware_map_find_entry_in_list(9) — yes the name is a whole mouthful, the header truncates it to firmware_ma...ntry_in_list(9) and honestly? relatable, she's long. anyway. it's a search function, it's tiny, it's iconic, let's go 🎀

---

🌸 NAME 🌸

firmware_map_find_entry_in_list — search a memmap entry in a given list. that's it. that's the whole job. finding a thing in a list. slay 💅

---

✨ SYNOPSIS ✨

struct firmware_map_entry * firmware_map_find_entry_in_list (u64 start ,
u64 end , const char *type , struct list_head *list );

look at her. returns a pointer to struct firmware_map_entry. takes four things. no cap, that's the whole signature 🫶

---

💜 ARGUMENTS 💜

• start — the start of the memory range. where the vibe begins ✨
• end — the end of the memory range. and bestie, it's exclusive — do not forget the exclusive part, it's giving "off by one" trap energy 😭
• type — the type of the memory range. gotta know what kind of range we're dealing with 🦋
• list — the list in which to find the entry. the search zone. the main character list 👑

---

🔥 DESCRIPTION 🔥

so what does she actually do? this function finds the memmap entry of a given memory range, inside a given list. literally that. find entry, in list. the name was not lying to you 💀

but here's the part you actually cannot skip, and I mean it, ngl this is the whole plot:

The caller must hold map_entries_lock, and must not release that lock until the processing of the returned entry has completed. 🔒

like, do not drop the lock early. do not pass go. hold map_entries_lock the entire time you're touching the returned entry. this is not a suggestion, this is the rules, periodt 🧚

---

⭐ RETURN ⭐

• pointer to the entry to be found on success 🎉
• NULL on failure 💀

that's the whole return contract. found it → you get the pointer. didn't find it → NULL, no drama, no error code, just vibes and NULL 🌈

---

🦋 SEE ALSO 🦋

kernel file ./drivers/firmware/memmap.c, plus the whole friend group:

• firmware_map_add_entry(9)
• firmware_map_remove_entry(9)
• firmware_map_find_entry(9)
• firmware_map_find_entry_bootmem(9)
• firmware_map_add_hotplug(9)
• firmware_map_add_early(9)
• firmware_map_remove(9)

go read them, iykyk 📚💖

---

and that's the page!! mwah 💋 this one lives under ./drivers/firmware, dated October 2026, and it's firmware_ma...ntry_in_list(9) all over again in the footer — we love a full circle moment 👑🌸 stay locked, stay hydrated, and hold that map_entries_lock 🫶✨