[SERVER-84120] Data race in waitForReadConcernImpl Created: 12/Dec/23  Updated: 03/Jan/24  Resolved: 03/Jan/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Sean Zimmerman Assignee: Sean Zimmerman
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2023-12-25, Repl 2024-01-08
Participants:
Linked BF Score: 120

 Description   

When setting the cached oplog Collection pointer in local_oplog_info we do so under the protection of the global lock. When we read the pointer we are not under lock which can lead to a data race.



 Comments   
Comment by Githook User [ 03/Jan/24 ]

Author:

{'name': 'seanzimm', 'email': '102551488+seanzimm@users.noreply.github.com', 'username': 'seanzimm'}

Message: SERVER-84120: Fail wait for read concern if we are in rollback state (#17576)

GitOrigin-RevId: 6532f833d02fe694d375f19e8c857b10f46de05e
Branch: master
https://github.com/mongodb/mongo/commit/74d2184f75f9e4678bea45025a76adcd1778e2a9

Comment by Louis Williams [ 12/Dec/23 ]

We should not hold a lock while doing a blocking wait, as this can lead to deadlocks.

Generated at Thu Feb 08 06:54:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.