Bug 1977042

Summary: systemd-journald terminated with signal SIGSEGV on 32 bit arm
Product: [Fedora] Fedora Reporter: Paul Whalen <pwhalen>
Component: systemdAssignee: systemd-maint
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: awilliam, fedoraproject, filbranden, flepied, kasong, kevin, lnykryn, msekleta, robatino, ssahani, s, systemd-maint, yuwatana, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: armhfp   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-20 23:58:00 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:
Bug Depends On:    
Bug Blocks: 245418, 1891953    

Description Paul Whalen 2021-06-28 20:02:17 UTC
Description of problem:

Booting recent rawhide disk images on armhfp systemd-journald is terminated with signal SIGSEGV.

systemctl --all --failed
  UNIT                            LOAD   ACTIVE SUB    DESCRIPTION                        
● systemd-journal-flush.service   loaded failed failed Flush Journal to Persistent Storage
● systemd-journald.service        loaded failed failed Journal Service                    
● systemd-journald-audit.socket   loaded failed failed Journal Audit Socket
● systemd-journald-dev-log.socket loaded failed failed Journal Socket (/dev/log)
● systemd-journald.socket         loaded failed failed Journal Socket

× systemd-journald.service - Journal Service
     Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
     Active: failed (Result: core-dump) since Mon 2021-06-28 15:00:12 EDT; 59min ago
TriggeredBy: × systemd-journald-dev-log.socket
             × systemd-journald.socket
             × systemd-journald-audit.socket
       Docs: man:systemd-journald.service(8)
             man:journald.conf(5)
    Process: 1296 ExecStart=/usr/lib/systemd/systemd-journald (code=dumped, signal=SEGV)
   Main PID: 1296 (code=dumped, signal=SEGV)
     Status: "Processing requests..."
        CPU: 287ms


Core was generated by `/usr/lib/systemd/systemd-journald'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xb6bcd2b0 in __convert_scm_timestamps (msg=msg@entry=0xbe9015a4, msgsize=msgsize@entry=328)
    at ../sysdeps/unix/sysv/linux/convert_scm_timestamps.c:90
90	  cmsg->cmsg_level = SOL_SOCKET;

Version-Release number of selected component (if applicable):
systemd-249~rc2-1.fc35.armv7hl

How reproducible:
Everytime, services are restarted but crash again shortly after.

Comment 1 Paul Whalen 2021-06-28 20:04:38 UTC
Created attachment 1795571 [details]
systemd-journald-sigsegv

Comment 2 Paul Whalen 2021-06-30 15:38:06 UTC
Proposing as a blocker for F35 Beta, criteria "Release-blocking ARM disk images must boot to the initial-setup utility.". This repeated crash buries initial-setup on the minimal armhfp image and breaks system logging.

Comment 3 Kevin Fenzi 2021-06-30 17:03:24 UTC
Could this have caused compose to fail today? but then why didn't it fail before?
https://pagure.io/releng/failed-composes/issue/2594

Comment 4 Paul Whalen 2021-07-05 20:47:10 UTC
No longer seeing this with systemd-249~rc3-1.fc35.

Comment 5 Adam Williamson 2021-07-20 23:58:00 UTC
OK, well, let's close the bug, then.