Hide Forgot
Description of problem: I have tried to compile refpolicy package in Fedora16. For standard policy type, coredump would occur in the "make load" step. Version-Release number of selected component (if applicable): libsemanage-2.1.2-1.fc16.i686 How reproducible: Always. Steps to Reproduce: 1. Download and extract refpolicy-2.20110726.tar.bz2 2. cd refplicy && edit build.conf TYPE = standard NAME = refpolicy DISTRO = redhat UNK_PERMS = allow DIRECT_INITRC = n MONOLITHIC = n CUSTOM_BUILDOPT = QUIET = n 3. make conf && make policy && make load Actual results: make: *** [load] Segmentation fault (core dumped) Expected results: build OK. Additional info: By backtrace, I found this occured in libsemanage/genhomedircon.c. When the "level" argument passed to set_fallback_user is NULL, strdup(NULL) would cause segfault. Below is the debug message I've seen: Program received signal SIGSEGV, Segmentation fault. __strlen_ia32 () at ../sysdeps/i386/i586/strlen.S:99 99 movl (%eax), %ecx /* get word (= 4 bytes) in question */ (gdb) bt #0 __strlen_ia32 () at ../sysdeps/i386/i586/strlen.S:99 #1 0x00303266 in __GI___strdup (s=0x0) at strdup.c:42 #2 0x0019642b in set_fallback_user (level=0x0, prefix=<optimized out>, user=<optimized out>, s=0xbf8916d0) at genhomedircon.c:665 #3 setup_fallback_user (s=0xbf8916d0) at genhomedircon.c:725 #4 write_context_file (out=0x28a4ef38, s=0xbf8916d0) at genhomedircon.c:918 #5 semanage_genhomedircon (sh=0x20ece068, policydb=0x25d95f10, usepasswd=0) at genhomedircon.c:1015 #6 0x0019a591 in semanage_direct_commit (sh=0x20ece068) at direct_api.c:967 #7 0x001a3f8d in semanage_commit (sh=0x20ece068) at handle.c:422 #8 0x00ec888c in main (argc=7, argv=0xbf891924) at semodule.c:470
Two additions: 1. For policy types of MCS/MLS, no problem. 2. This could be worked around by specifying "disable-genhomedircon = true" in semanage.conf - Thanks.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.