Skip to content

fix(sync): tighten Send and Sync contracts for locks and guards - #579

Closed
Natural-selection1 wants to merge 1 commit into
vivoblueos:mainfrom
Natural-selection1:codex/lock-send-sync-probe
Closed

Natural-selection1 wants to merge 1 commit into
vivoblueos:mainfrom
Natural-selection1:codex/lock-send-sync-probe

Conversation

@Natural-selection1

Copy link
Copy Markdown
Contributor

Keep SpinLock and RwLock guards on the acquiring thread, including across RwLock upgrades and downgrades. Use the same NotThreadSafe marker for guards that restore IRQ, preemption, syscall or flash mutex state. IrqTrace in particular decrements the current CPU's IRQ nesting count on drop.

A shared SpinLock can lend out a write guard that replaces its payload.
Require T: Send + Sync when sharing SpinLock or ISpinLock, and require
Send on the boxed AArch64 ISR handlers owned by the interrupt registry.

Keep SpinLock and RwLock guards on the acquiring thread, including across
RwLock upgrades and downgrades. Use the same NotThreadSafe marker for
guards that restore IRQ, preemption, syscall or flash mutex state.
IrqTrace in particular decrements the current CPU's IRQ nesting count
on drop. Keep these context guards Sync so shared references can still
be borrowed across threads.
@Natural-selection1
Natural-selection1 marked this pull request as draft November 19, 2026 09:53
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