db_for_each_64(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… db_for_each_64(9) β€” the kernel API manual, bestie edition πŸŽ€

okay so we're in the db_for_each_64(9) page of the Kernel API Manual and honestly it's giving "tiny function, big main character energy" ✨ stick with me.


🌸 NAME 🌸

db_for_each_64 β€” the iterator for 64 bit entries, periodt πŸ’–


✨ SYNOPSIS ✨

int db_for_each_64 (const struct os_area_db *db , const struct
os_area_db_id *match_id , struct db_iterator *i );

lowkey that's the whole vibe right there 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • db β€” so the manpage itself literally just says -- undescribed -- 😭 like the docs said "figure it out bestie". Not me making stuff up though, no cap β€” that's all it says. πŸ™ˆ
  • match_id β€” also -- undescribed -- πŸ’€ same energy, the source was busy.
  • i β€” and yep, -- undescribed -- too πŸŽ€ the trio of mystery arguments, iconic honestly.
fr fr, I'm not gonna invent descriptions for these β€” the original page doesn't describe them, so neither do I. if you wanna know more, go read the headers, iykyk πŸ‘‘

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the actual tea πŸ“: a NULL value for id can be used to match all entries. like, every single one. the whole roster. main character matching energy πŸ’…

and it's not just NULL β€” you can also use OS_AREA_DB_OWNER_ANY and OS_AREA_DB_KEY_ANY to match all. so that's three whole ways to say "yeah give me everything" πŸŒˆπŸ’–


🌟 SEE ALSO 🌟

the whole friend group, assembled 🫢 go say hi:


and that's the page!! πŸ’œ this lil gem lives under ./arch/powerpc/platforms/ps3, and it's dated October 2026 β€” future-coded of it tbh ⭐ slay, go read the rest of the kernel docs, mwah πŸ§šβ€β™€οΈπŸ’–

πŸ“¦ where this page comes from