mirrors/arti.git/crates/fslock-guard/src, branch arti-v1.1.13 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.13 2024-01-24T17:20:58Z fslock-guard: Add links to documentation about windows approach 2024-01-24T17:20:58Z Nick Mathewson nickm@torproject.org 2024-01-24T17:20:58Z urn:sha1:2869361c9263d01c12fb20854492f1c6207f6051 fslock-guard: use winapi to test file-equivalency on windows 2024-01-23T20:44:47Z Nick Mathewson nickm@torproject.org 2024-01-23T20:44:47Z urn:sha1:bd52d43779ed3a61d000bf16e96ed09ad924e141 fslockguard: try to document windows assumptions 2024-01-23T20:01:42Z Nick Mathewson nickm@torproject.org 2024-01-23T17:52:34Z urn:sha1:849650b6c9e59e14130f23df7a28a3f1c7c38b99 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. 2024-01-23T20:01:42Z Nick Mathewson nickm@torproject.org 2024-01-23T17:37:25Z urn:sha1:145fba4946fca21e80b9b5ae85d7da5944ad17f3 fslockguard: implement a delete_lock_file function. 2024-01-23T20:01:42Z Nick Mathewson nickm@torproject.org 2024-01-23T17:35:20Z urn:sha1:b9b8463973ef883a01e50d151fd0bc1104fe7156 Use fslock-arti-fork 2024-01-23T20:01:42Z Nick Mathewson nickm@torproject.org 2024-01-22T16:08:22Z urn:sha1:dae9c9afacc85eb6d9b791b5b1c924a9a25aba83 fslock-guard: Write down the locking protocol on Unix 2024-01-23T14:06:06Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-01-23T14:00:26Z urn:sha1:015dc1034a8e836c172b46d560bb9f64fad3e80e 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 2024-01-23T13:56:29Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-01-23T13:53:49Z urn:sha1:9eb247ad99b44fcf04f17afa78b6f37731b9e815 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. 2024-01-22T17:36:01Z Ian Jackson iwj@torproject.org 2024-01-22T17:36:01Z urn:sha1:b5e7d921dd3bd578b2014b392fa39dec4a0c3110 fslock-guard: sketch implementation 2024-01-21T21:51:25Z Nick Mathewson nickm@torproject.org 2024-01-21T21:46:27Z urn:sha1:70815226d086473152ec98a5ae8341ef4d067be3 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.)