Skip to content

checklocks: guard the TCP segment queue - #14259

Closed
tamird wants to merge 1 commit into
google:masterfrom
tamird:checklocks-tcp-segment-queue
Closed

checklocks: guard the TCP segment queue#14259
tamird wants to merge 1 commit into
google:masterfrom
tamird:checklocks-tcp-segment-queue

Conversation

@tamird

@tamird tamird commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

The segment queue uses mu for its list and frozen state, but checklocks does not enforce that ownership. Guard both fields and enforce the existing caller-held lock requirement of emptyLocked.

Assisted-by: Codex

@tamird

tamird commented Aug 21, 2026

Copy link
Copy Markdown
Contributor Author

r? @nybidari for the segment queue field guards and existing helper precondition. Local TCP analysis, unit, and receive tests passed. The broader TCP end-to-end target is blocked here by baseline Linux-only build dependencies on macOS.

cc @konstantin-s-bogom

Assisted-by: Codex

The segment queue uses mu for its list and frozen state, but checklocks
does not enforce that ownership. Guard both fields and enforce the
existing caller-held lock requirement of emptyLocked.

Assisted-by: Codex
@tamird
tamird force-pushed the checklocks-tcp-segment-queue branch from 6c22efb to 5ef194b Compare August 21, 2026 23:08
@tamird

tamird commented Aug 23, 2026

Copy link
Copy Markdown
Contributor Author

Closing in favor of consolidated #14338. The expanded replacement commits are prepared locally; the replacement branch has not been pushed yet.

Assisted-by: Codex

@tamird tamird closed this Aug 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant