[SERVER-84626] The state of RenameCollectionParticipantService should be protected by a mutex Created: 08/Jan/24 Updated: 11/Jan/24 Resolved: 11/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: | Paolo Polato | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | CAR Team 2024-01-08, CAR Team 2024-01-22 | ||||
| Participants: | |||||
| Linked BF Score: | 21 | ||||
| Description |
|
It has been recently discovered that the recovery document of RenameCollectionParticipantService is not protected by any synchronisation primitive, exposing the component to potential data race scenarios (for example, doc attributes could be read to compose the response to $currentOp while the doc itself is being replaced). |
| Comments |
| Comment by Githook User [ 11/Jan/24 ] |
|
Author: {'name': 'ppolato', 'email': '82828243+ppolato@users.noreply.github.com', 'username': 'ppolato'}Message: GitOrigin-RevId: 37501b2150baea9d055f1ab8477e06352eb12a85 |