Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Fix SIGSEGV on exit when an EAP method is referenced (v3.0.x) #1591
Conversation
lytboris
changed the title from
Fix SIGSEGV on exit when an EAP method is referenced to Fix SIGSEGV on exit when an EAP method is referenced (v3.0.x)
Apr 25, 2016
|
I don't see why this is necessary. The dlopen / dlclose API takes care of reference counting the handles. From the "man" page for dlopen:
In this case, if |
alandekok
closed this
Apr 25, 2016
lytboris
referenced
this pull request
Apr 25, 2016
Closed
Fix SIGSEGV on exit when an EAP method is referenced (v3.1.x) #1590
lytboris
commented
Apr 26, 2016
|
I tracked it down. My patch IS correct. Take a look on When module is loaded, no dlopen() is invoked and handle is left as 0x0. The only thing to fix for this patch is to fix the comment. |
arr2036
reopened this
Apr 26, 2016
|
Heh yeah, I guess that was added to support static compilation of EAP methods into rlm_eap. |
|
I think we still need to call the detach method though, that's probably per rlm_eap instance. If we don't call it we leak memory on HUP |
lytboris
commented
Apr 26, 2016
|
detach pointer may reference freed memory when real rlm_eap_... method was unloaded previously invalidating type pointer. |
arr2036
added a commit
that referenced
this pull request
Apr 26, 2016
|
|
arr2036 |
cf9cda6
|
lytboris commentedApr 25, 2016
in multiple eap stansas, e.g.
eap instance1 {
...
md5 {
}
...
}
eap instance2 {
...
md5 {
}
...
}
Sponsored by: Yandex LLC