mirrors/arti.git/crates/tor-proto/src/relay/reactor.rs, branch arti-v2.0.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.02026-01-29T16:33:21Zproto: Remove unused async from relay reactor2026-01-29T16:33:21ZGabriela Moldovangabi@torproject.org2026-01-29T16:21:11Zurn:sha1:7cfe5a3768e94249a32bde081590203f2dea0393
Fixes a clippy warning
proto: Replace relay reactor with new generic reactor2026-01-29T16:33:21ZGabriela Moldovangabi@torproject.org2026-01-26T18:40:43Zurn:sha1:bc26b037e03cc7ae25b69e9e8ac99527c5fcb8b0proto: Avoid locking in CircHopOutbound::ccontrol()2026-01-29T16:33:21ZGabriela Moldovangabi@torproject.org2026-01-22T11:54:26Zurn:sha1:29159e80c713ea4ab1ab657c7eeae53f37e62814
This is just because the generic reactor will soon need a clone of the
CC object, so I am preemptively making this function return a ref to the
underlying `Arc` instead. Technically, it would've been fine to just
kept this method and add a separate one returning `&Arc<Mutex<..>>`,
but I'd prefer keeping the API small.
proto: Rip CC state out of CircHopInbound2026-01-29T16:33:21ZGabriela Moldovangabi@torproject.org2026-01-16T16:51:17Zurn:sha1:ce6c90cca94b02e6d78d7cca7f01ec4f675f4c28
Soon it won't need be needed here any more. I'm removing it, because
having redundant handles to the CC state makes it difficult to see
exactly where it's being used from.
proto: Dedupe IncomingStreamRequestHandler2026-01-12T19:10:54ZGabriela Moldovangabi@torproject.org2026-01-12T18:50:26Zurn:sha1:271603e38f5be23ae3ff756a18fb87406a933e9dproto: Give IncomingStreamRequestHandler a HopNum2026-01-12T19:10:43ZGabriela Moldovangabi@torproject.org2026-01-12T18:44:14Zurn:sha1:c4c13c63c40374370f5a61dfd6f97c40478c528a
This currently duplicates the client `IncomingStreamRequestHandler`.
To deduplicate it, we need the `hop_num` to be optional (it will be
`None` for relays, and `Some(hopnum)` in the client reactor).
The next commit will fix the code duplication.
proto: Relay circuit reactor now handles AnyChanMsg2025-12-10T16:04:26ZDavid Gouletdgoulet@torproject.org2025-12-08T19:35:45Zurn:sha1:252cff2fb8e40b37e28b4faff8abb47862fabb7c
Same as the client reactor, a message outside of our restricted set
leads to a reactor shutdown.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Move RelayCircChanMsg into relay module2025-12-10T16:03:12ZDavid Gouletdgoulet@torproject.org2025-12-08T18:22:07Zurn:sha1:6a14dc2b478a41f7f2ee54b307a746c22ced233f
This follows the move of the client specific object.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Fix relay/hs-service feature gating (fmt)2025-12-08T17:40:08ZGabriela Moldovangabi@torproject.org2025-12-08T17:40:08Zurn:sha1:5020e1e2add42450252512f4eb628e95409cc7d4proto: Fix relay/hs-service feature gating2025-12-08T17:39:08ZGabriela Moldovangabi@torproject.org2025-12-08T17:39:08Zurn:sha1:f033030c559ec75e0a4a26b69a1e15ca66a7e0d7
Without this, `tor-proto` doesn't compile if you enable the `relay`
feature but not `hs-service`.