mirrors/arti.git - mirror of https://gitlab.torproject.org/tpo/core/arti

	Commit message (Collapse)	Author	Age	Files	Lines
*	fslock-guard: Add links to documentation about windows approach	Nick Mathewson	2024-01-24	1	-0/+7
\|
*	fslock-guard: use winapi to test file-equivalency on windows	Nick Mathewson	2024-01-23	1	-6/+19
\|
*	fslockguard: try to document windows assumptions	Nick Mathewson	2024-01-23	1	-0/+41
\| \| \| \| \|	These are necessarily a bit hand-wavey, but I think they summarize what we are assuming.
*	Remove an XXX: fslock does indeed use O_CLOEXEC.	Nick Mathewson	2024-01-23	1	-1/+0
\|
*	fslockguard: implement a delete_lock_file function.	Nick Mathewson	2024-01-23	1	-3/+29
\|
*	Use fslock-arti-fork	Nick Mathewson	2024-01-23	1	-19/+6
\|
*	fslock-guard: Write down the locking protocol on Unix	Ian Jackson	2024-01-23	1	-0/+65
\| \| \| \| \| \|	Text from here https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1900#note_2986683 with a few minor fixes.
*	fslock-guard: Rename os modules	Ian Jackson	2024-01-23	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \|	These two modules are key to the implementation of the locking protocols. We must define the locking protocol in terms of underlying OS semantics (since Unix and Windows have different fs concepts and different concurrency semantics) and therefore, although we are sharing some code between the implementations, these modules are what defines the two protocols.
*	Give a formal semantics for the fslock operations.	Ian Jackson	2024-01-22	1	-0/+15
\|
*	fslock-guard: sketch implementation	Nick Mathewson	2024-01-21	1	-0/+149
	This is not yet "correct", since it will rely on https://github.com/brunoczim/fslock/pull/15 (Conceivably, it might be better to make the `fslock` crate rm-safe.)