Bug 621200
| Summary: | [abrt] systemd-units-5-2.fc15: selabel_lookup_common: Process /bin/systemctl was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeff Layton <jlayton> | ||||||||
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | rawhide | CC: | awilliam, eparis, frankly3d, genes1122, jlaska, jmoskovc, lpoetter, metherid, mike, mnowak, mschmidt, nicolas.mailhot, notting, rhe, selinux, steved | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | abrt_hash:c1d4a4d6aeb09eb75045fe65db4ac18f1e255ca8 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2010-08-11 19:36:11 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Jeff Layton
2010-08-04 14:05:52 UTC
Created attachment 436547 [details]
File: backtrace
The SELinux handle (label_hnd) was NULL. systemctl does not call label_init()... Created attachment 436563 [details]
patch which allows it to not segfault
Jeff or Eric: What's the fallout of this issue? Does it prevent boot, or cause spewage during the boot process? Neither -- I saw it spew the message while patching the machine, and again when I tried to follow the directions here to see if it would fix my systemd problems: http://lists.fedoraproject.org/pipermail/devel/2010-August/140294.html (hint: it didn't) A different patch has been merged upstream. Will upload a fixed version to f14 today. Eric, thanks for your patch! *** Bug 621584 has been marked as a duplicate of this bug. *** Created attachment 436914 [details]
Here is my patch. You want to execute the fini or valgrind will complain about memmory leak
*** Bug 621658 has been marked as a duplicate of this bug. *** *** Bug 621681 has been marked as a duplicate of this bug. *** we need this to be open to track getting it fixed for the f14 alpha compose; we need a build that fixes this before we can go ahead with the RC. scratch that, i just tested and it doesn't prevent boot with 5-2. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #12) > scratch that, i just tested and it doesn't prevent boot with 5-2. I suppose if you already had systemd-4 installed and working, then upgrading to systemd-5-2 will not break you boot. But a segfaulting systemctl must be pretty bad for new installs, because the tool is used to enable essential services in postinstall scriptlets of systemd-units and dbus. do we know exactly what operation triggered the systemctl fail? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** Bug 621697 has been marked as a duplicate of this bug. *** (In reply to comment #14) > do we know exactly what operation triggered the systemctl fail? systemctl enable $ANY_SYSTEMD_UNIT as long as SELinux is enabled (enforcing or permissive). ah. so, yes, that does seem very likely to break new installs. looks like we will need a fix for this. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Package: systemd-units-5-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Branched) How to reproduce ----- systemctl enable graphical.target systemd-6-1.fc14 has been submitted as an update for Fedora 14. http://admin.fedoraproject.org/updates/systemd-6-1.fc14 (In reply to comment #17) > ah. so, yes, that does seem very likely to break new installs. looks like we > will need a fix for this. Yeah I agree ... seems to touch on the following release criteria (https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria) "In most cases, the installed system must boot to a functional graphical environment without user intervention" Moving to ON_QA as an update is available with this fix. (In reply to comment #21) > (In reply to comment #17) > > ah. so, yes, that does seem very likely to break new installs. looks like we > > will need a fix for this. > > Yeah I agree ... seems to touch on the following release criteria > (https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria) > > "In most cases, the installed system must boot to a functional graphical > environment without user intervention" > > Moving to ON_QA as an update is available with this fix. F14-Alpha-RC2 still used systemd-5-2, therefore caused default.target (and other links) not to be created in the postinstall scriptlets when SELinux is enabled.(bug#618315) (In reply to comment #22) > (In reply to comment #21) > > (In reply to comment #17) > > > ah. so, yes, that does seem very likely to break new installs. looks like we > > > will need a fix for this. > > > > Yeah I agree ... seems to touch on the following release criteria > > (https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria) > > > > "In most cases, the installed system must boot to a functional graphical > > environment without user intervention" > > > > Moving to ON_QA as an update is available with this fix. > > F14-Alpha-RC2 still used systemd-5-2, therefore caused default.target (and > other links) not to be created in the postinstall scriptlets when SELinux is > enabled.(bug#618315) Sorry, I made a mistake. Systemd-5-2 was installed by net-install with branched repo. But DVDs contain the right 6-2 version. *** Bug 622475 has been marked as a duplicate of this bug. *** 7-1 has the fix for this and is stable and in alpha rc3, so closing. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reopening bug. This bug was opened against rawhide and the latest package in rawhide is 5-2. Please build the newer package for rawhide (fc15) and then close the bug. *** Bug 623433 has been marked as a duplicate of this bug. *** Build going out for F-15 now. This doesn't block F14 Alpha, even if it's not fixed in Rawhide. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers |