[SERVER-8275] Potential signal/malloc deadlock in mongos Created: 22/Jan/13 Updated: 06/Dec/22 Resolved: 19/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Sharding |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | mongos, triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
If mongos receives SIGTERM or SIGINT on a thread that holds the malloc mutex, the signal handler may deadlock since it mallocs as part of string construction. I have not observed this deadlock. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 19/Apr/18 ] |
|
We removed memory allocation from signal handlers in 2.6. |
| Comment by Andy Schwerin [ 22/Jan/13 ] |
|
This bug has existed for a very long time in our product. It's hard to tickle, and not especially harmful. I'd fix in 2.5. |