rgblk_free(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rgblk_free β€” a Kernel API Manual moment (section 9, bestie)

okay so picture this: it's a rgblk_free(9) kind of day and we're out here changing the alloc state of given block(s). That's literally the whole name, no notes. πŸŽ€


✨ NAME ✨

rgblk_free β€” Change alloc state of given block(s)

Like, you hand it some blocks and it goes "cool, new state for you bestie" and rewrites their allocation status. Slay.


πŸ¦‹ SYNOPSIS πŸ¦‹

void rgblk_free (struct gfs2_sbd *sdp , struct gfs2_rgrpd *rgd , u64
bstart , u32 blen , unsigned char new_state );

Returns void. It gives nothing back and honestly? That's main character energy. πŸ‘‘


🌸 ARGUMENTS 🌸

  • sdp β€” the filesystem. the whole vibe, the big picture, the struct gfs2_sbd in question πŸ’–
  • rgd β€” the resource group the blocks are in. lowkey important to know where we're at
  • bstart β€” the start of a run of blocks to free. the launch point, the beginning of the run πŸš€
  • blen β€” the length of the block run. and bestie, listen to me: all must lie within ONE RG! not two, not "mostly one", ONE. okay? πŸ˜­πŸ™
  • new_state β€” GFS2_BLKST_XXX, the after-allocation block state. it's giving "this is what the block identifies as now" ✨
ngl the blen caveat is the one that will get you. every single block in the run has to live inside that one resource group, periodt. don't come crying to me when you ignore it πŸ’€

🌈 SEE ALSO 🌈

Kernel file ./fs/gfs2/rgrp.c β€” and honestly the whole friend group showed up:

like, the entire rgrp cinematic universe. iykyk 🫢


anyway that's the tea πŸ“ β€” this page came to you from ./fs/gfs2, dated October 2026, and it's filed under rgblk_free(9) in the Kernel API Manual. go free those blocks bestie, and remember: ONE RG. πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from