Version-Release number of selected component: systemd-udev-239-6.git9f3aed1.fc29 Additional info: reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-udevd crash_function: __libc_open64 executable: /usr/lib/systemd/systemd-udevd journald_cursor: s=30a647b59ecc4c30bb3896dfe65d299f;i=413e4;b=ae684aefafff46c3b018aa20aa23f1f8;m=2c09738b5;t=57c37ccee12ba;x=236d7c45870eb660 kernel: 4.19.5-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (9 frames) #0 __libc_open64 at ../sysdeps/unix/sysv/linux/open64.c:43 #1 open64 at /usr/include/bits/fcntl2.h:53 #2 synthesize_change at ../src/udev/udevd.c:1028 #3 on_inotify at ../src/udev/udevd.c:1137 #4 source_dispatch at ../src/libsystemd/sd-event/sd-event.c:3103 #5 sd_event_dispatch at ../src/libsystemd/sd-event/sd-event.c:3516 #6 sd_event_run at ../src/libsystemd/sd-event/sd-event.c:3573 #7 sd_event_loop at ../src/libsystemd/sd-event/sd-event.c:3595 #8 run at ../src/udev/udevd.c:1627 Potential duplicate: bug 1520506
Created attachment 1521863 [details] File: backtrace
Created attachment 1521864 [details] File: cgroup
Created attachment 1521865 [details] File: core_backtrace
Created attachment 1521866 [details] File: cpuinfo
Created attachment 1521867 [details] File: dso_list
Created attachment 1521868 [details] File: environ
Created attachment 1521869 [details] File: limits
Created attachment 1521870 [details] File: maps
Created attachment 1521871 [details] File: mountinfo
Created attachment 1521872 [details] File: open_fds
Created attachment 1521873 [details] File: proc_pid_status
SIGABRT in open() looks like the watchdog kicked in and killed the process. Is your machine resource-starved and/or do you have hardware issues with /dev/sdb?
*** Bug 1669782 has been marked as a duplicate of this bug. ***
*** Bug 1672728 has been marked as a duplicate of this bug. ***
*** Bug 1683582 has been marked as a duplicate of this bug. ***
I hope this is already fixed in upstream by https://github.com/systemd/systemd/commit/70068602713e8f441c5ddc2618f007f24488e422. Previously, the argument of open() was given by udev_device_get_devnode() and its return value was not checked. By the commit, return value is checked, so now open() should have a valid path argument.
*** Bug 1688594 has been marked as a duplicate of this bug. ***
*** Bug 1690455 has been marked as a duplicate of this bug. ***
*** Bug 1692705 has been marked as a duplicate of this bug. ***
I don't think 70068602713e8f441c5ddc2618f007f24488e422 can explain this. If udev_device_get_devnode() fails, it returns NULL. But here the path pointer is non-NULL. Also, the signal doesn't match. An invalid pointer would give SIGSEGV, and not SIGABRT.
Yep, in all the bugs marks as duplices, the devnode argument is either /dev/sdb or /dev/sdc. In this one, gdb says it cannot read the pointer, but the uevent filename is /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/host6/target6:0:0/6:0:0:0/block/sdb/uevent, so it's /dev/sdb again. *** This bug has been marked as a duplicate of bug 1300212 ***
*** Bug 1711084 has been marked as a duplicate of this bug. ***
*** Bug 1720046 has been marked as a duplicate of this bug. ***