[SERVER-62824] Fix `op_msg_fuzzer` initialization order on v4.4 Created: 20/Jan/22  Updated: 29/Oct/23  Resolved: 21/Jan/22

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.4.13

Type: Bug Priority: Major - P3
Reporter: Amirsaman Memaripour Assignee: Amirsaman Memaripour
Resolution: Fixed Votes: 0
Labels: servicearch-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Service Arch 2022-1-24
Participants:
Linked BF Score: 34
Story Points: 1

 Description   

The fuzzer test for op_msg creates a Client before reseting the global instance of AuthorizationManager. This causes sanitizer failures as we may try to access the deleted instance of AuthorizationManager through the client. Creating the client after setting AuthorizationManager should resolve the issue.

This is a test-only issue on v4.4. The code on the master branch is currently 8 commits ahead of v4.4, and backporting those 8 commits is not clean (they depend on features not backported to v4.4).



 Comments   
Comment by Githook User [ 21/Jan/22 ]

Author:

{'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}

Message: SERVER-62824 Fix `op_msg_fuzzer` initialization order on v4.4
Branch: v4.4
https://github.com/mongodb/mongo/commit/af94205826d1db93ddab1a308ec77d52bfbbb28e

Generated at Thu Feb 08 05:56:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.