8 matches found
Filelock: SoftFileLock Removes A Live Holder's Marker When Another User Forges The PID In A Writable Marker
"SoftFileLock", "MarkerSoftFileLock", "SoftFileLease", their async variants and a "FileLock" that has fallen back to a soft lock on "ENOSYS" decide from the record inside the marker file whether its owner is gone. The marker is the file whose presence says a process holds the lock. They do not...
Filelock: SoftFileLock Stale-lock Break Removes A Live Lock File On A Reused Inode Number And Admits Two Holders
The stale-lock break shared by "SoftFileLock", "MarkerSoftFileLock" and "SoftFileLease" and their async variants, and a "FileLock" that has fallen back to a soft lock on "ENOSYS", the "not implemented" error recognises the marker it judged stale by two values. The marker is the lock file at "",...
GHSA-RFPC-QCW5-3PC4 filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker
SoftFileLock, MarkerSoftFileLock, SoftFileLease, their async variants and a FileLock that has fallen back to a soft lock on ENOSYS decide from the record inside the marker file whether its owner is gone. The marker is the file whose presence says a process holds the lock. They do not check who...
filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker
SoftFileLock, MarkerSoftFileLock, SoftFileLease, their async variants and a FileLock that has fallen back to a soft lock on ENOSYS decide from the record inside the marker file whether its owner is gone. The marker is the file whose presence says a process holds the lock. They do not check who...
GHSA-FQ56-3CX3-FJXP filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders
The stale-lock break shared by SoftFileLock, MarkerSoftFileLock and SoftFileLease and their async variants, and a FileLock that has fallen back to a soft lock on ENOSYS, the "not implemented" error recognises the marker it judged stale by two values. The marker is the lock file at , whose presenc...
filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders
The stale-lock break shared by SoftFileLock, MarkerSoftFileLock and SoftFileLease and their async variants, and a FileLock that has fallen back to a soft lock on ENOSYS, the "not implemented" error recognises the marker it judged stale by two values. The marker is the lock file at , whose presenc...
Filelock: SoftFileLock Stale-break Restore Follows A Swapped-in Symbolic Link And Hard-links A File Of The User Running
When a soft-lock stale break finds that the marker the lock file at "" it renamed aside was a live one recreated by a successor, the restore branch of "breaklockfile" checks the break name with "lstat" a check that reads a name without following a symbolic link and then calls "os.linkbreakpath,...
Filelock: SoftFileLock Evicts A Fresh Lock File Whose Watched Age Another Local User's Pre-dated File Passed On Through
"SoftFileLock" and "MarkerSoftFileLock" evict an unparsable marker the lock file at "", whose presence says a process holds the lock once a waiting contender has watched it unchanged for two seconds. "SoftFileLease" expires a lease the same way. The watch tells two looks apart by the marker's...