Description of problem: I received this at the end of anaconda installation when debugging bug 1157657. It is probably caused by bug 1157770 - selinux denial. Version-Release number of selected component: mdadm-3.3.2-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/sbin/mdadm --detail --export /dev/md126p1 crash_function: strcpy executable: /usr/sbin/mdadm kernel: 3.17.1-302.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #1 strcpy at /usr/include/bits/string3.h:104 #2 super_by_fd at util.c:1064 #3 Detail at Detail.c:109 #4 misc_list at mdadm.c:1778
Created attachment 951064 [details] File: backtrace
Created attachment 951065 [details] File: cgroup
Created attachment 951066 [details] File: core_backtrace
Created attachment 951067 [details] File: dso_list
Created attachment 951068 [details] File: environ
Created attachment 951069 [details] File: exploitable
Created attachment 951070 [details] File: limits
Created attachment 951071 [details] File: maps
Created attachment 951072 [details] File: mdstat_data
Created attachment 951073 [details] File: open_fds
Created attachment 951074 [details] File: proc_pid_status
Created attachment 951075 [details] File: var_log_messages
Another user experienced a similar problem: Trying to run an install with anaconda. I was also running firefox with the lastpass password manager to try reporting a (probably related) python-blivet bug. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/sbin/mdadm --detail --export /dev/md126p2 crash_function: strcpy executable: /usr/sbin/mdadm kernel: 3.17.1-302.fc21.x86_64 package: mdadm-3.3.2-1.fc21 reason: mdadm killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
I'm now seeing this bug with what should be a still-intact and functioning hardware raid with an old Fedora 20 install/partitions and NTFS data partition. I also saw a selinux report pop up. So I think these bugs are still hanging around. This was hit using the current Beta release iso.
In my case, this actually caused anaconda to fail at the start of the install. See Bug#1160424
Meaning before even selecting language during a Live boot - no drive selections made or anything.
I'm sorry - I mistyped earlier. This is an Intel firmware raid, not a hardware raid.
I also saw this when doing a firmware RAID install over an existing firmware RAID install. The install completed apparently successfully, however.
Please retest with mdadm-3.3.4 for F21/F22 Jes
Sorry, that was a one-time issue and I can't reproduce the setup anymore.
Thanks for the update! In that case I am going to close the bug since it cannot be reproduced. If you experience it again, please feel free to open a new bugzilla. Cheers, Jes
Ditto here, yeah. I'm fine with leaving it closed.