Cap per-connection recv drain to prevent poll-loop starvation (fixes #76)#77
Draft
cursor[bot] wants to merge 1 commit into
Draft
Cap per-connection recv drain to prevent poll-loop starvation (fixes #76)#77cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
A peer that keeps its kernel recv buffer full could monopolize process_connections() and starve every other session until the socket was drained. Limit each connection to 256 KiB per poll pass. Co-authored-by: Alexander Wagner <info@alexanderwagnerdev.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Security fix: server recv fairness cap
Fixes #76
Finding
Severity: Medium (availability / DoS)
Location:
src/server/mod.rsProblem
Server::process_connections()drained each peer's entire kernel recv buffer in an unbounded inner loop before servicing the next connection. A single high-volume sender could monopolize the single-threaded poll loop and starve every other session on the sameServer.Fix
Introduce
MAX_RECV_BYTES_PER_CONN_PER_POLL(256 KiB) and stop recv-draining a connection once that budget is exhausted for the current poll pass. Remaining bytes are picked up on the nextpoll()call, giving other connections a turn.Impact
Prevents connection-starvation DoS against co-located RTMP sessions without affecting normal throughput (256 KiB per poll is sufficient for steady-state media).
Tests
server::tests::recv_budget_is_at_least_one_socket_readserver::tests::recv_budget_is_small_enough_for_fairness_across_connectionscargo test --no-default-featuresgreenNeed help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.