vfs_inode_has_locks(9)

✨ NAME ✨

okay so bestie, welcome to the vfs_inode_has_locks(9) page from the Kernel API Manual — it's giving “one tiny locks vibe check” and we're obsessed 💅

vfs_inode_has_locks — are any file locks held on @inode? 🎀

✨ SYNOPSIS ✨

bool vfs_inode_has_locks (struct inode *inode );

✨ ARGUMENTS ✨

• inode — the inode to check for locks, no cap 🦋

✨ DESCRIPTION ✨

so this function returns true if there are any FL_POSIX or FL_FLOCK locks currently set on inode. that's it, that's the tea ☕ periodt.

👀 SEE ALSO 👀

• Kernel file ./fs/locks.c
• locks_owner_has_blockers(9)
• lease_open_conflict(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)

okay that's the whole page! source/version: ./fs, date: October 2026, and the page is vfs_inode_has_locks(9) — bye bestie, mwah 💋✨