lockd_set_file_lock_range3(9)

💅 lockd_set_file_lock_range3(9) 💅

okay so bestie, this is the lockd_set_file_lock_range3(9) page from the Kernel API Manual — yes, we're doing kernel lock ranges today and it's lowkey iconic ✨

🌸 NAME 🌸

lockd_set_file_lock_range3 — set the byte range of a file_lock

🦋 SYNOPSIS 🦋

void lockd_set_file_lock_range3 (struct file_lock *fl , u32 off , u32
       len );

🎀 ARGUMENTS 🎀

• fl — the file_lock whose length fields are to be initialized 🫶
• off — starting offset of the lock, in bytes
• len — length of the byte range, in bytes, or zero

✨ DESCRIPTION ✨

okay so here's the tea: NLMv3 uses a (start, length) representation for lock byte ranges, while the kernel's file_lock uses (start, end). literally two different vibes bestie 😭

Treat a length of zero or arithmetic overflow — that's when end wraps negative because the sum exceeds S32_MAX — as "lock to end of file." 💅

no cap: zero length and that overflow case both mean the lock goes all the way to the end of the file. periodt.

🔥 SEE ALSO 🔥

• Kernel file ./fs/lockd/lockd.h
• lockd_set_file_lock_range4(9)

mwah 💋 this page's source/version is ./fs/lockd, its date is October 2026, and it's all about lockd_set_file_lock_range3(9) — bye bestie, go set those ranges! 🫶✨