gfs2_alloc_size(9)

💅 gfs2_alloc_size(9) — from the Kernel API Manual, bestie ✨

okay so picture this: you're deep in the GFS2 filesystem, right, and you need to know how big your next allocation can possibly be. That's literally this function. It's giving "main character of the block allocator" energy 👑

---

🌸 NAME 🌸

gfs2_alloc_size — compute the maximum allocation size 💖

---

✨ SYNOPSIS ✨

u64 gfs2_alloc_size(struct inode *inode, struct metapath *mp, u64 size);

---

🎀 ARGUMENTS 🎀

• inode — the inode, the whole reason we're here 🫶
• mp — the metapath (iykyk)
• size — the requested size, measured in blocks 🧮

---

🦋 DESCRIPTION 🦋

So the actual job? Compute the maximum size of the next allocation at mp. That's it. That's the whole vibe. Lowkey elegant, ngl ✨

---

⭐ RETURN ⭐

The size in blocks 🔥

---

🌈 SEE ALSO 🌈

Kernel file ./fs/gfs2/bmap.c, plus the whole friend group 💅:

• gfs2_unstuffer_folio(9)
• gfs2_unstuff_dinode(9)
• find_metapath(9)
• metaptr1(9)
• metapointer(9)
• lookup_metapath(9)
• fillup_metapath(9)
• gfs2_extent_length(9)
• gfs2_hole_size(9)
• __gfs2_iomap_alloc(9)
• __gfs2_iomap_get(9)
• gfs2_block_map(9)
• gfs2_journaled_truncate(9)
• sweep_bh_for_rgrps(9)
• find_nonnull_ptr(9)
• punch_hole(9)
• do_shrink(9)
• do_grow(9)
• gfs2_setattr_size(9)
• gfs2_free_journal_extents(9)
• gfs2_add_jextent(9)
• gfs2_map_journal_extents(9)
• gfs2_write_alloc_required(9)

---

and that's the page, bestie 🎀 it lives in ./fs/gfs2, the version vibes are dated October 2026, and the whole thing answers to the name gfs2_alloc_size(9). slay, go read some kernel source 💜