[SERVER-50463] Make PooledLDAPConnection::refresh take self-ownership Created: 21/Aug/20 Updated: 29/Oct/23 Resolved: 26/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | 4.5.1, 4.0.19, 4.2.8, 4.4.0 |
| Fix Version/s: | 4.7.0, 4.2.10, 4.4.2, 4.0.21 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Shreyas Kalyan |
| Resolution: | Fixed | Votes: | 1 |
| 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: |
v4.4, v4.2, v4.0
|
||||||||||||
| Sprint: | Security 2020-09-07 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
PooledLDAPConnection::refresh schedules a job which validates the wrapped LDAP connection. Under some circumstances, it appears that the pool is able to reap the connection while this job is outstanding, causing a segmentation fault. We should ensure that the connection takes ownership of itself for the duration of the refresh job, just as the TLConnection::refresh method does. |
| Comments |
| Comment by Githook User [ 18/Sep/20 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: (cherry picked from commit c9c006b5d7778fdf6539941d49a24324bccf1e93) |
| Comment by Githook User [ 18/Sep/20 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: (cherry picked from commit c9c006b5d7778fdf6539941d49a24324bccf1e93) |
| Comment by Githook User [ 17/Sep/20 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: |
| Comment by Githook User [ 25/Aug/20 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: |