gfs2_next_unreserved_block(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… gfs2_next_unreserved_block β€” Kernel API Manual, section 9 πŸ¦‹

okay so bestie, we're in the kernel API manual (section 9, the fun one) and today's main character is gfs2_next_unreserved_block ✨


🌸 NAME 🌸

gfs2_next_unreserved_block β€” returns the next block that is not reserved, no cap πŸ’…


✨ SYNOPSIS ✨

u64 gfs2_next_unreserved_block (struct gfs2_rgrpd *rgd , u64 block , u32
length , struct gfs2_blkreserv *ignore_rs );

literally just copy that signature exactly, don't be weird about it 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • rgd β€” the resource group. yes. that one. πŸ‘‘
  • block β€” the starting block, aka where we begin the hunt πŸ•΅οΈβ€β™€οΈ
  • length β€” the required length. we need this much, fr fr πŸ“
  • ignore_rs β€” the reservation to ignore πŸ™ˆ like we're pretending it's not even there

πŸ’– DESCRIPTION πŸ’–

so here's the vibe check πŸ”₯ if the block does not appear in any reservation, then we return the block number unchanged β€” no notes, no edits, she stays exactly as she came in πŸ’…

but if it does appear in the reservation? that's when we go looking πŸ‘€ we keep looking through the tree of reservations in order to find the first block number which is not reserved. that's the whole gig. that's the mission. slay 🌈


🧚 SEE ALSO 🧚

kernel file ./fs/gfs2/rgrp.c β€” and the entire group chat of friends, all present and accounted for, nobody left on read:

like… fifty of them?? and every single one made the list. iconic behavior honestly πŸ’€πŸ‘‘


lowkey reminder bestie: this page is living in ./fs/gfs2 and it's stamped October 2026 β€” that's the source folder and the date, keep them safe 🫢

and that's the page!! mwah πŸ’‹ β€” signed off from the Kernel API Manual, gfs2_next_unreserved_block(9), dated October 2026, source ./fs/gfs2. periodt. 🌟

πŸ“¦ where this page comes from