nilfs_sufile..._alloc_range(9)

💖 NAME 💖

nilfs_sufile_set_alloc_range — okay bestie, welcome to the nilfs_sufile..._alloc_range(9) page from the Kernel API Manual ✨ this function’s whole job is to limit range of segment to be allocated, and it is lowkey iconic for it 💅

✨ SYNOPSIS ✨

Here’s the exact signature, no edits, no cap:

int nilfs_sufile_set_alloc_range (struct inode *sufile , __u64 start ,
       __u64 end );

🎀 ARGUMENTS 🎀

• sufile — the inode of segment usage file, aka the main character of this whole operation 🫶
• start — the minimum segment number of allocatable region (inclusive) 🌸
• end — the maximum segment number of allocatable region (inclusive) 🦋

🌈 RETURN 🌈

Returns 0 on success, or -ERANGE if segment range is invalid — that’s the vibe check, and if it fails, it fails 😭

🦋 SEE ALSO 🦋

Bestie, if you wanna go deeper, the Kernel file is ./fs/nilfs2/sufile.c, and here’s the whole squad:

• struct nilfs_sufile_info(9)
• nilfs_sufile_segment_usage_offset(9)
• nilfs_sufile_get_ncleansegs(9)
• nilfs_sufile_updatev(9)
• nilfs_sufile_alloc(9)
• nilfs_sufile_mark_dirty(9)
• nilfs_sufile_set_segment_usage(9)
• nilfs_sufile_get_stat(9)
• nilfs_sufile_truncate_range(9)
• nilfs_sufile_resize(9)
• nilfs_sufile_get_suinfo(9)
• nilfs_sufile_set_suinfo(9)
• nilfs_sufile_trim_fs(9)
• nilfs_sufile_read(9)

Signed off with sparkle from the ./fs/nilfs2 source tree, October 2026 edition of nilfs_sufile..._alloc_range(9) — stay slay, bestie 💅💖✨