mirrors/arti.git/crates/fslock-guard, branch arti-v1.1.13mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.132024-02-05T16:13:29ZBump minor versions2024-02-05T16:13:29ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-05T16:13:29Zurn:sha1:af615d87e20d0984f493dfb8dda7b0654d8d7304
Bump the minor version of these crates, and update the in-tree
dependencies.
Recently published as fresh crates, let's just assume there are
breaking changes:
fslock-guard
test-temp-dir
Breaking API change affecting many many downstream crates:
tor-rtcompat
Downstream crates which we're (conservatively) assuming have
tor-rtcompat types in their APIs:
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-hspow
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-congestion
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
fslock-guard: Add links to documentation about windows approach2024-01-24T17:20:58ZNick Mathewsonnickm@torproject.org2024-01-24T17:20:58Zurn:sha1:2869361c9263d01c12fb20854492f1c6207f6051fslock-guard: use winapi to test file-equivalency on windows2024-01-23T20:44:47ZNick Mathewsonnickm@torproject.org2024-01-23T20:44:47Zurn:sha1:bd52d43779ed3a61d000bf16e96ed09ad924e141fslockguard: try to document windows assumptions2024-01-23T20:01:42ZNick Mathewsonnickm@torproject.org2024-01-23T17:52:34Zurn: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:42ZNick Mathewsonnickm@torproject.org2024-01-23T17:37:25Zurn:sha1:145fba4946fca21e80b9b5ae85d7da5944ad17f3fslockguard: implement a delete_lock_file function.2024-01-23T20:01:42ZNick Mathewsonnickm@torproject.org2024-01-23T17:35:20Zurn:sha1:b9b8463973ef883a01e50d151fd0bc1104fe7156Use fslock-arti-fork2024-01-23T20:01:42ZNick Mathewsonnickm@torproject.org2024-01-22T16:08:22Zurn:sha1:dae9c9afacc85eb6d9b791b5b1c924a9a25aba83fslock-guard: Write down the locking protocol on Unix2024-01-23T14:06:06ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-23T14:00:26Zurn: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 modules2024-01-23T13:56:29ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-23T13:53:49Zurn: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:01ZIan Jacksoniwj@torproject.org2024-01-22T17:36:01Zurn:sha1:b5e7d921dd3bd578b2014b392fa39dec4a0c3110