Bug 1548417
Summary: | systemd crashed and froze execution | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 27 | CC: | lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-11-21 13:31:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tom Horsley
2018-02-23 12:58:44 UTC
Thanks, that's a pretty good backtrace. I'll take a look at the code, but no promises: looks like some kind of memory corruption, and those are hard to debug, especially when non-repeatable.
> Why isn't systemd two processes. A traditional init that does nothing but reap zombies and can restart the complicated chunk of code when it crashes like this?
This has been discussed endlessly on the internets. This isn't the venue for this kind of discussions.
We are trying to clean up the old udev code upstream, but it's going slowly (ETA is F30 or F31). F27 is too old at this point. Sorry not being able to handle this. |