Description of problem: Happens at boot time. Also reported in bugzilla id=1642071 Version-Release number of selected component: e2fsprogs-1.43.8-2.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: dumpe2fs -h /dev/sdb5 crash_function: e2p_is_null_uuid executable: /usr/sbin/dumpe2fs journald_cursor: s=333235b510ab49eaba1ef6236d3c1a20;i=23c7;b=940197441a8547339d2098169e54b38f;m=33788b4e;t=578d45dcca7e2;x=da0e908b5ce4bb59 kernel: 4.16.3-301.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #0 e2p_is_null_uuid at uuid.c:32 #1 e2p_uuid2str at uuid.c:80 #2 e2p_list_journal_super at ljs.c:105 #3 print_inline_journal_information at dumpe2fs.c:395 Potential duplicate: bug 1565797
Created attachment 1496896 [details] File: backtrace
Created attachment 1496897 [details] File: cgroup
Created attachment 1496898 [details] File: core_backtrace
Created attachment 1496899 [details] File: cpuinfo
Created attachment 1496900 [details] File: dso_list
Created attachment 1496901 [details] File: environ
Created attachment 1496902 [details] File: exploitable
Created attachment 1496903 [details] File: limits
Created attachment 1496904 [details] File: maps
Created attachment 1496905 [details] File: mountinfo
Created attachment 1496906 [details] File: open_fds
Created attachment 1496907 [details] File: proc_pid_status
Thanks for the report. This should be fixed with upstream commit commit b0ec76d623f737a32abc5ab8bb7198bf1d9939a4 Author: Lukas Czerner <lczerner> Date: Tue Aug 14 16:37:53 2018 +0200 libe2p: avoid segfault when s_nr_users is too high Currently in e2fsprogs tools it's possible to access out of bounds memory when reading list of ids sharing a journal log (journal_superblock_t->s_users[]) in case where s_nr_users is too high. This is because we never check whether the s_nr_users fits into the restriction of JFS_USERS_MAX. Fix it by checking that nr_users is not bigger than JFS_USERS_MAX and error out when possiblem. Also add test for dumpe2fs. The rest would require involving external journal which is not possible to test with e2fsprogs test suite at the moment. Signed-off-by: Lukas Czerner <lczerner> Signed-off-by: Theodore Ts'o <tytso> Will be updating e2fsprogs once a new version is released. Thanks! -Lukas
e2fsprogs-1.44.6-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b4207428d3
e2fsprogs-1.44.6-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b4207428d3
e2fsprogs-1.44.6-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.