Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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