lease_open_conflict(9)

💖 lease_open_conflict(9) 💖

hey bestie 👋 welcome to the Kernel API Manual — this is the lease_open_conflict(9) page, and it’s lowkey a little vibe check for file leases. no cap, let’s get into it 💅

🌸 NAME 🌸

lease_open_conflict — see if the given file points to an inode that has an existing open that would conflict with the desired lease.

✨ SYNOPSIS ✨

int lease_open_conflict (struct file *filp , const int arg );

🫶 ARGUMENTS 🫶

• filp — the file to check, bestie.
• arg — the type of lease that we’re trying to acquire.

💫 DESCRIPTION 💫

okay so the whole assignment: check to see if there’s an existing open fd on this file that would conflict with the lease we’re trying to set. that’s the entire tea ☕✨

👑 SEE ALSO 👑

Kernel file ./fs/locks.c and the whole lock-adjacent friend group: locks_owner_has_blockers(9), locks_delete_block(9), posix_lock_file(9), posix_lock_inode_wait(9), inode_lease_ignore_mask(9), __break_lease(9), lease_get_mtime(9), __fcntl_getlease(9), generic_setlease(9), vfs_setlease(9), fcntl_setlease(9), fcntl_setdeleg(9), flock_lock_inode_wait(9), locks_lock_inode_wait(9), sys_flock(9), vfs_test_lock(9), locks_translate_pid(9), vfs_lock_file(9), vfs_cancel_lock(9), vfs_inode_has_locks(9).

mwah 💋 — source/version ./fs, dated October 2026, and the page is still lease_open_conflict(9). byeee 🦋