dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
e2fsprogs (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
when using gnome control center (no idea, if related)
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: e2fsprogs 1.44.4-2
ProcVersionSign
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Date: Fri Oct 5 19:27:27 2018
ExecutablePath: /sbin/dumpe2fs
InstallationDate: Installed on 2018-10-05 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181004)
ProcCmdline: dumpe2fs -h /dev/sdc1
SegvAnalysis:
Segfault happened at: 0x7fa1b9836ffc <e2p_is_
PC (0x7fa1b9836ffc) ok
source "$0x0" ok
destination "-0x1(%rdi)" (0x7ffcdb8f3000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: e2fsprogs
StacktraceTop:
e2p_is_null_uuid () from /lib/x86_
e2p_uuid2str () from /lib/x86_
e2p_list_
?? ()
?? ()
Title: dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
StacktraceTop: entry=0x7ffcdb8 f3000) at ../../. ./../lib/ e2p/uuid. c:32 entry=0x7ffcdb8 f3000) at ../../. ./../lib/ e2p/uuid. c:80 journal_ super (f=0x7fa1b95de760 <_IO_2_1_stdout_>, journal_ sb_buf= 0x7ffcdb8f1db0 "\300;9\230", exp_block_ size=4096, flags=<optimized out>) at ../../. ./../lib/ e2p/ljs. c:105 inline_ journal_ information (fs=0x555fb1e382d0) at ../../. ./misc/ dumpe2fs. c:395 ./misc/ dumpe2fs. c:733
e2p_is_null_uuid (uu=uu@
e2p_uuid2str (uu=uu@
e2p_list_
print_
main (argc=<optimized out>, argv=<optimized out>) at ../../.