[SERVER-37898] CollectionCloner must not set _clientConnection without holding _mutex Created: 02/Nov/18  Updated: 29/Oct/23  Resolved: 08/Nov/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.6

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
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 2018-11-19
Participants:
Linked BF Score: 56

 Description   

The CollectionCloner sets _clientConnection without holding _mutex. This causes _cancelRemainingWork_inlock() to be able to read bad state. _clientConnection must only be set while holding _mutex. It is expected that _clientConnection is always set when _queryState is kRunning.



 Comments   
Comment by Githook User [ 08/Nov/18 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-37898 CollectionCloner must not set _clientConnection without holding _mutex
Branch: master
https://github.com/mongodb/mongo/commit/1dbb12023ff57af62a9daee85cf7637432231b5f

Generated at Thu Feb 08 04:47:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.