Skip to content

checklocks: guard signal recipient state - #14330

Closed
tamird wants to merge 1 commit into
google:masterfrom
tamird:checklocks-signal-recipients
Closed

checklocks: guard signal recipient state#14330
tamird wants to merge 1 commit into
google:masterfrom
tamird:checklocks-signal-recipients

Conversation

@tamird

@tamird tamird commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Enforce FileAsync's registration and notification state guards, and TTY.mu ownership of controlling-terminal associations. Distinguish direct waiter-entry access under regMu from the waitable's own synchronization.

Preserve registration lock ordering and signal delivery after releasing FileAsync.mu, while leaving TTY's signal-delivery lock scope unchanged.

Assisted-by: Codex

Enforce FileAsync's registration and notification state guards, and
TTY.mu ownership of controlling-terminal associations. Distinguish
direct waiter-entry access under regMu from the waitable's own
synchronization.

Preserve registration lock ordering and signal delivery after releasing
FileAsync.mu, while leaving TTY's signal-delivery lock scope unchanged.

Assisted-by: Codex
@tamird

tamird commented Aug 22, 2026

Copy link
Copy Markdown
Contributor Author

r? @shailend-g Could you review FileAsync/TTY ownership and signal-delivery lock boundaries?

Focused local Bazel checks passed. Upstream checks have not reported yet.

Assisted-by: Codex

@tamird

tamird commented Aug 23, 2026

Copy link
Copy Markdown
Contributor Author

Closing in favor of consolidated #14345. 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