Version-Release number of selected component: e2fsprogs-1.42.12-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: dumpe2fs crash_function: strlen executable: /usr/sbin/dumpe2fs kernel: 3.18.7-200.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:106 #1 ext2fs_open2 at openfs.c:142 #2 ext2fs_open at openfs.c:93
Created attachment 993328 [details] File: backtrace
Created attachment 993329 [details] File: cgroup
Created attachment 993330 [details] File: core_backtrace
Created attachment 993331 [details] File: dso_list
Created attachment 993332 [details] File: environ
Created attachment 993333 [details] File: exploitable
Created attachment 993334 [details] File: limits
Created attachment 993335 [details] File: maps
Created attachment 993336 [details] File: open_fds
Created attachment 993337 [details] File: proc_pid_status
Created attachment 993338 [details] File: var_log_messages
I assume you invoked dumpe2fs with no arguments? [root e2fsprogs]# misc/dumpe2fs dumpe2fs 1.42.12 (29-Aug-2014) Segmentation fault :/
commit fecb231f6fc83cf4b4ddf7ec34ace3723803a499 Author: Darrick J. Wong <darrick.wong> Date: Fri Nov 7 21:26:14 2014 -0500 dumpe2fs: don't crash when the user provides no block device argument If the user doesn't provide any arguments, the guard fails to run and the whole thing segfaults on ext2fs_open2(). Don't do that. Signed-off-by: Darrick J. Wong <darrick.wong> Signed-off-by: Theodore Ts'o <tytso>
This commit from v1.42.12 regressed this behavior: commit 20d6b381a1aacfdb553dcba95d96c5bf36ea7253 Author: Theodore Ts'o <tytso> Date: Sun Aug 24 22:31:03 2014 -0400 dumpe2fs: complain if extra arguments are given on the command line Addresses-Debian-Bug: #758074 Signed-off-by: Theodore Ts'o <tytso>
I didn't call dumpe2fs directly at all. I don't know what call caused the crash, I was trying 'Disks' (the Gnome disk manager) and 'Partition Manager' (the KDE disk manager) when the error happened. I just at some point recognized abrt telling me an error occurred and I then sent the report.
Ok, weird. > cmdline: dumpe2fs I guess that was the whole backtrace. I wonder which tool called it like that.
It was all that abrt reported, I didn't remove anything.
yes, I understand, I just wonder why some other utility called it w/ no args. anyway, I know the fix, it'll be in the (sigh) next update. Thanks for the report. :) -Eric
Maybe I can give a hint... I installed kde-partitionmanager right before (according to logs 30 seconds) that crash was noticed by abrt. /var/log/yum.log: <snip> Feb 23 12:25:28 Installed: kde-partitionmanager-1.1.0-3.fc21.x86_64 </snip> abrt-cli list <snip> reason: dumpe2fs killed by SIGSEGV time: Mon 23 Feb 2015 12:25:57 PM CET cmdline: dumpe2fs </snip> So I might have started kde-partitionmanager right before dumpe2fs which could explain _who_ called it without arguments. Anyway, shouldn't crash anyhow IMHO.
e2fsprogs-1.42.12-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/e2fsprogs-1.42.12-3.fc21
e2fsprogs-1.42.12-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/e2fsprogs-1.42.12-3.fc20
Package e2fsprogs-1.42.12-3.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing e2fsprogs-1.42.12-3.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2511/e2fsprogs-1.42.12-3.fc21 then log in and leave karma (feedback).
e2fsprogs-1.42.12-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
e2fsprogs-1.42.12-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1201554 has been marked as a duplicate of this bug. ***