nvdimm_badblocks_populate(9)

💜 nvdimm_badblocks_populate(9)

okay so bestie, welcome to the Kernel API Manual — this one's a tiny little function in ./drivers/nvdimm and honestly it's giving "small but iconic" 🎀

---

✨ NAME ✨

nvdimm_badblocks_populate — the glow-up where a list of badranges becomes actual badblocks 💅

---

🌸 SYNOPSIS 🌸

void nvdimm_badblocks_populate (struct nd_region *nd_region , struct
badblocks *bb , const struct range *range );

like, yes, that's the whole signature, no cap 🫶

---

🦋 ARGUMENTS 🦋

• nd_region — the parent region of the range you're interrogating 👀 (it's the main character, everything hangs off it)
• bb — the badblocks instance you're populating. this is the one getting filled up, she's literally the canvas 💖
• range — the resource range to consider. the zone you're checking against, iykyk

---

🔥 DESCRIPTION 🔥

so here's the tea, bestie:

the badrange list that gets generated during bus initialization may contain multiple ranges — and yes, they might possibly be overlapping physical address ranges 😭 like nobody said it was gonna be clean.

what this function does: it compares each of those ranges to the resource range that's currently being initialized, and then adds badblocks entries for all the matching sub-ranges. every single match. no skipping, no shortcuts. periodt ✨

it's literally just a conversion moment — badranges in, badblocks out 🧚

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/nvdimm/badrange.c
• __add_badblock_range(9)

---

💀 reminder: this whole page is Kernel API Manual territory, so if you're poking at badrange.c without a good reason, bestie, maybe go touch some grass first 🙈🌱

---

okay that's the whole page!! 🍓 source: ./drivers/nvdimm, dated October 2026, from your favorite Kernel API Manual — go forth and populate those badblocks correctly, mwah 💋👑