Hide Forgot
Description of problem: Every time I start the storaged service with systemd, it segfaults. I also can reproduce the error by simply running /usr/libexec/storaged/storaged in a root terminal. # /usr/libexec/storaged/storaged 16:12:39.885:[20329]:[NOTICE]: storaged daemon version 2.2.0 starting [main.c:153, main()] 16:12:39.888:[20329]:[DEBUG]: Entering main event loop [main.c:178, main()] 16:12:39.905:[20329]:[DEBUG]: Modules unloading, detaching interfaces... [storagedlinuxprovider.c:481, ensure_modules()] 16:12:39.905:[20329]:[DEBUG]: Performing coldplug... [storagedlinuxprovider.c:503, ensure_modules()] 16:12:39.915:[20329]:[DEBUG]: uevent add /sys/devices/virtual/block/dm-0 [storagedlinuxprovider.c:1183, storaged_linux_provider_handle_uevent()] 16:12:39.916:[20329]:[DEBUG]: Looking for x-parent=44ccdd40-810a-4b83-9ad7-89be3af70c8d [storagedlinuxblock.c:834, find_configurations()] Segmentation fault (core dumped) I can reproduce this issue at will if you need further debugging. This particular instance, I passed the --disable-modules flag, but it happens with or without that flag in place. Version-Release number of selected component: storaged-2.2.0-3.el7 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/libexec/storaged/storaged --disable-modules crash_function: strstr executable: /usr/libexec/storaged/storaged global_pid: 28685 kernel: 3.10.0-327.13.1.el7.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 strstr at /lib64/libc.so.6 #1 storaged_linux_find_child_configuration at storagedlinuxblock.c:813 #4 storaged_linux_encrypted_update at storagedlinuxencrypted.c:114 #6 encrypted_update at storagedlinuxblockobject.c:704 #7 update_iface at storagedlinuxblockobject.c:394 #8 storaged_linux_block_object_uevent at storagedlinuxblockobject.c:808 #9 storaged_linux_block_object_constructed at storagedlinuxblockobject.c:236 #10 g_object_new_internal at /lib64/libgobject-2.0.so.0 #11 g_object_new_valist at /lib64/libgobject-2.0.so.0 #13 storaged_linux_block_object_new at storagedlinuxblockobject.c:308
Created attachment 1143997 [details] File: backtrace
Created attachment 1143998 [details] File: cgroup
Created attachment 1143999 [details] File: core_backtrace
Created attachment 1144000 [details] File: dso_list
Created attachment 1144001 [details] File: environ
Created attachment 1144002 [details] File: limits
Created attachment 1144003 [details] File: machineid
Created attachment 1144004 [details] File: maps
Created attachment 1144005 [details] File: open_fds
Created attachment 1144006 [details] File: proc_pid_status
Created attachment 1144007 [details] File: var_log_messages
Created attachment 1144008 [details] File: sosreport.tar.xz
I have a core file as well if needed.
Can you, please, verify that this build works for you? https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=10809143 Thank you.
Updated build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=10823537
I tested storaged-2.2.0-4.el7 with the patch set Peter developed and it appears to work properly. Thank you very much.
Note, the original patch set from 2016-04-08 didn't include a crucial chunk of code and did not work. The successful test was the 2016-04-11 version of the packages.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1571.html