Bug 484595
Summary: | segfault in libselinux cleanup functions | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | DaveT <davetickem> |
Component: | libselinux | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | drepper, dwalsh, mgrepl, sct |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/237156 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-28 11:12:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
DaveT
2009-02-08 20:28:29 UTC
This is actually just exposing a bug in the transcode package and should be reported to them. The libselinux library is just freeing up memory in it's destructor. We have had a few other packages that this code has tirggered errors. Uli can explain better then I. I'll close until I can prove otherwise, (If I can...). Reopening, I've just been bitten by this same transcode issue on F10 i386, and it does appear to be a libselinux fault. gdb shows the problem is occurring in the libselinux destructor: static void fini_lib(void) __attribute__ ((destructor)) calls hidden void fini_context_translations(void) calls free(prev_r2t_trans); where this variable is thread-local: static __thread security_context_t prev_r2t_trans = NULL; In this particular case, libselinux is being dlopen'ed implicitly by the dlopen'ing of the transcode filter-resample.so DSO. When that DSO is dlclosed, libselinux is having its destructor called, but I don't think it's legal to access TLS from that context. I chatted with Eric Paris about this for a bit. He believes that this has been fixed in rawhide libselinux, and indeed, rebuilding the current libselinux/devel source on F10 fixes the transcode problem for me. He also pointed me at http://www.engardelinux.org/modules/index/list_archives.cgi?list=selinux&page=0014.html&month=2009-05 http://www.engardelinux.org/modules/index/list_archives.cgi?list=selinux&page=0039.html&month=2009-07 where this destructor problem is discussed further. Miroslav can you see about back porting the libselinux functionality to F10 and F11. This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |