[SERVER-41056] Fix NiTL::shutdown() without startup() Created: 08/May/19 Updated: 29/Oct/23 Resolved: 08/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Networking |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| 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 2019-05-20 | ||||||||
| Participants: | |||||||||
| Description |
|
It should be legal to call shutdown() on a network interface without calling startup() (because an owning task executor will call shutdown() in its dtor). Currently this crashes (because the NiTL doesn't keep track of whether it's started). Changing the _inShutdown atomic to a _state enum atomic can resolve that problem |
| Comments |
| Comment by Githook User [ 08/May/19 ] |
|
Author: {'email': 'jcarey@argv.me', 'name': 'Jason Carey', 'username': 'hanumantmk'}Message: It should be legal to call shutdown() on a network interface without Currently this crashes (because the NiTL doesn't keep track of whether |