[SERVER-63852] getThreadName() should not crash Created: 18/Feb/22 Updated: 29/Oct/23 Resolved: 13/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.12, 6.0.2, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergey Galtsev (Inactive) | 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 | ||||||||||||||||||||||||||||||||
| Backport Requested: |
v6.0, v5.0
|
||||||||||||||||||||||||||||||||
| Sprint: | Service Arch 2022-05-16, Service Arch 2022-05-30 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||||||||||
| Description |
|
If getThreadName() is invoked before ThreadContextsInitialized is complete, a SIGSEGV will happen. The name is typically needed for debugging and logging purposes and should not cause a crash. This ticket is to implement a mitigation to SIGSEGV |
| Comments |
| Comment by Billy Donahue [ 22/Aug/22 ] |
|
Message: Branch: v5.0 |
| Comment by Billy Donahue [ 22/Aug/22 ] |
|
Message: Branch: v6.0 |
| Comment by Githook User [ 13/May/22 ] |
|
Author: {'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}Message: |
| Comment by Blake Oler [ 28/Mar/22 ] |
|
sergey.galtsev It looks like you already have a potential solution here – would you mind putting it up for code review and tagging Service Arch as reviewers? |