Repeated segfault in udev_rule_line_free

Bug #1936236 reported by PyroDesu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu version: 20.04 focal (Distro: Linux Mint 20.1 Ulyssa)

systemd version: 245.4-4ubuntu3.7

What happened: systemd-udevd underwent repeated segfaults and coredumps for unknown reasons. Loop stopped by forcing restart of udevd. Coredump information:

           PID: 381 (systemd-udevd)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Wed 2021-07-14 00:12:29 EDT (9h ago)
  Command Line: /lib/systemd/systemd-udevd
    Executable: /lib/systemd/systemd-udevd
 Control Group: /system.slice/systemd-udevd.service
          Unit: systemd-udevd.service
         Slice: system.slice
       Boot ID: abaa4a5b0c6641cda2c58d7c307cfc38
    Machine ID: b76cc7b1bbdc489e93909d2043031de8
      Hostname: Ampere-Limux
       Storage: /var/lib/systemd/coredump/core.systemd-udevd.0.abaa4a5b0c6641cda2c58d7c307cfc38.381.1626235949000000000000.lz4
       Message: Process 381 (systemd-udevd) of user 0 dumped core.

                Stack trace of thread 381:
#0 0x00005635cdf522eb in udev_rule_line_free (rule_line=0x5635cec9db20) at ../src/udev/udev-rules.c:270
#1 0x00005635cdf53d0c in udev_rule_file_free (rule_file=0x5635cecb2760) at ../src/udev/udev-rules.c:289
#2 udev_rules_free (rules=0x5635cea0ad10) at ../src/udev/udev-rules.c:302
#3 0x00005635cdf60875 in manager_free (manager=manager@entry=0x5635ce9fde60) at ../src/udev/udevd.c:306
#4 0x00005635cdf63e34 in manager_freep (p=<synthetic pointer>) at ../src/udev/udevd.c:314
#5 run (argc=<optimized out>, argv=<optimized out>) at ../src/udev/udevd.c:1703
#6 0x00005635cdf0721a in main (argc=<optimized out>, argv=<optimized out>) at ../src/udev/udevd.c:1817

Revision history for this message
Nick Rosbrook (enr0n) wrote :

Sorry this was not looked at sooner. Please re-open if still an issue.

Changed in systemd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.