[SERVER-64427] Init-order fiasco in secure_allocator Created: 10/Mar/22 Updated: 29/Oct/23 Resolved: 11/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Billy Donahue | Assignee: | Billy Donahue |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Service Arch 2022-03-21 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 167 | ||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
Init-order fiasco in secure_allocator. It accesses a namespace scope hash table to construct namespace scope objects. These are the newly changed:
in this case ( This is not going to work unless the link order accidentally makes it work. Affecting ASAN in mongodb-mongo-master waterfall. The secure allocator has to be ALWAYS available, including for the initialization of global static duration objects and must be alive during their destruction. Hide all such instances behind local static immortals. |
| Comments |
| Comment by Githook User [ 11/Mar/22 ] |
|
Author: {'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}Message: |
| Comment by Billy Donahue [ 10/Mar/22 ] |
|
This is a very quick fix. Pulling it into sprint. |