[SERVER-10236] Make logging work during thread destruction Created: 17/Jul/13 Updated: 26/Sep/16 Resolved: 26/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.5.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Done | 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: | Platforms 2016-10-10 | ||||||||
| Participants: | |||||||||
| Description |
|
When a thread terminates, objects pointed to by Thread Specific Pointers (TSPs), also known as Thread Local Storage (TLS), are deleted. One of these thread-local objects is used for logging. If the logging TSP is deleted before another TSP and the later TSP tries to log anything in its destructor, this can cause a segfault. The code should be modified to guarantee that the TSP used for logging is the last TSP to be deleted so that other thread-local objects can use the logging system during object destruction. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 26/Sep/16 ] |
|
This ticket was filed to remind us to remove the workaround added in in this commit: https://github.com/mongodb/mongo/commit/2cf30807f82d325ef706211667cd80e008e8ca68. However, in Therefore, I'm closing this issue as 'Gone Away'. |
| Comment by Eliot Horowitz (Inactive) [ 27/Nov/13 ] |
|
When this is done, we need to make sure to revert changes in |