filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name

filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout

filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files

filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders

filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lock

filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse

filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path