OF-3358: Publish the SASL mechanism registry as an immutable snapshot - #3476
Conversation
initMechanisms assigned an empty set and then filled it, so a concurrent reader could observe a partial mechanism list. The field was not volatile either, giving readers no happens-before edge to a writer at all. The registry is now replaced wholesale rather than mutated in place, and the three writers are synchronized. Readers are unchanged.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthrough
Merge Risk: ⚪ Minimal · up to The PR publishes complete immutable SASL mechanism snapshots and serializes updates, preventing readers from observing partially initialized configuration without changing authentication controls. No actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
initMechanisms assigned an empty set and then filled it, so a concurrent reader could observe a partial mechanism list. The field was not volatile either, giving readers no happens-before edge to a writer at all.
The registry is now replaced wholesale rather than mutated in place, and the three writers are synchronized. Readers are unchanged.