mirrors/arti.git/crates/tor-hsservice/src/replay.rs, branch arti-v1.2.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.02024-03-01T01:10:33ZMake test_partial_write linux-only.2024-03-01T01:10:33ZNick Mathewsonnickm@torproject.org2024-03-01T01:10:33Zurn:sha1:0d28fad5ba7470818020695f41bf69505b6a07a2
This is a temporary workaround for #1307:
In `libc`, struct sigaction doesn't seem to have
the same fields on all the unix platforms.
tor-hsservice: replay: Fix an error message slightly2024-02-13T18:54:42ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-13T17:17:04Zurn:sha1:096fc0969ab8a2ad1b0206f62ddb27cf91d62dd0
On Windows filenames are WTF-16, not bytes, so a weird filename fails
to be UTF-16 rather than failing to be UTF-8.
tor-hsservice: replay: Move replay filename knowledge into replay.rs (fmt)2024-02-13T18:54:42ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-13T17:15:29Zurn:sha1:5ce1deba462d9e1c85ec6c78965a190d87e3403ctor-hsservice: replay: Move replay filename knowledge into replay.rs2024-02-13T18:54:42ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-13T12:40:32Zurn:sha1:78b07cb15bb793b4b7483dc75bd9d609d66b4118tor-hsservice: replay log test: Check SIGUSR2 status on entry2024-02-12T15:46:15ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-08T19:19:26Zurn:sha1:5bfd3488ea0cddd326d59333c10899aee92ad230
Will make the situation in #1264 clear, I think.
tor-hsservice: replay log test: Break out sigemptyset()2024-02-12T15:46:13ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-08T19:19:14Zurn:sha1:91e4d8f53cd43e198b4ecc614a2dc6d9b08b0646tor-hsservice: replay log test: Plumb output manually2024-02-12T15:46:13ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-08T19:01:58Zurn:sha1:209edaa2830c1962c9ed3a13a1ca6c2a5cba7d4f
Something libtest is doing hides the child stderr/stdout from the test
log, when --nocapture is not given.
With these changes, I see much more output in failing cases or with
--nocapture. In the case mentioned in #1264, the message
"we survived raise SIGUSR2" is now printed both with and without --nocapture.
Fix compilation with musl.2024-02-06T13:16:25ZNick Mathewsonnickm@torproject.org2024-02-06T13:16:25Zurn:sha1:95de7b79ed12daece43e2dfc64eb3232e1752c2b
Don't try to name the type of `RLIMIT_FSIZE` in our tests:
its type is either `c_int` or `__rlimit_resource_t` depending on
the libc instance.
Closes #1264.
tor-hsservice: Drop now-unused fslock dependency2024-02-01T11:21:44ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-30T15:52:16Zurn:sha1:fa943898292e3110cba343064b2f48ad9f661a25
We're just using fslock-guard now.
tor-hsservice: Use tor_persist::state_dir2024-02-01T11:21:44ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-30T15:42:13Zurn:sha1:b4a7f0fca0d231eb9c0298b78deee9ed3c1bbc7e
We no longer do replay log locking in IptManager::new. Instead, we
rely on the acquire_instance call in OnionService::launch, which ends
up with ipt_mgr getting an InstanceHandle (which contains a lock
guard).
OnionServiceStateMgr is abolished; it existed to deal with the
generics in the tor_persist::StateMgr API. state_dir has no
generics (other than the T being loaded/stored).
Many places (structs and argument lists) now have state_dir types
which embody a path (or a CheckeDir) along with a lock, rather than
separate path+lock+mistrust.
The creation/startup code uses the new calls from state_dir.
Other more minor changes:
- StartupError::StateDirectoryInaccessible contains tor_persist::Error
- test::create_storage_handles_from_state_dir changed and renamed,
from _from_state_mgr.
- replay::PersistFile's (separate) file lock is now fslock_guard's