[SERVER-19538] Segfault when calling dbexit in SSLManager with auditing enabled Created: 23/Jul/15 Updated: 24/Aug/15 Resolved: 28/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | 3.0.4 |
| Fix Version/s: | 3.0.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Quint Iteration 7 |
| Participants: |
| Description |
|
The following sequence of events trigger the segfault.
There are no dependencies between the initialization of the auditing code and the SSLManager, so an fassert occurs when the order of events (2) and (3) are reversed. |
| Comments |
| Comment by Githook User [ 28/Jul/15 ] | |||||||||||||||||||||||||
|
Author: {u'name': u'Ramon Fernandez', u'email': u'ramon@mongodb.com'}Message: Revert "Revert " This reverts commit a466693f46fdd7a539dc99389a7258c9290ed3aa. | |||||||||||||||||||||||||
| Comment by Githook User [ 27/Jul/15 ] | |||||||||||||||||||||||||
|
Author: {u'username': u'ramonfm', u'name': u'Ramon Fernandez', u'email': u'ramon.fernandez@mongodb.com'}Message: Revert " This reverts commit b6cc64fab37049438a061e93946b0aa4a5b15686. | |||||||||||||||||||||||||
| Comment by Githook User [ 27/Jul/15 ] | |||||||||||||||||||||||||
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: | |||||||||||||||||||||||||
| Comment by Max Hirschhorn [ 23/Jul/15 ] | |||||||||||||||||||||||||
|
Per discussion with milkie, we shouldn't call dbexit() in the SSLManager. Andy fixed this as part of his CurOp changes in
|