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.
Bug 1720903 - e2fsck segfaults on exit
Summary: e2fsck segfaults on exit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: e2fsprogs
Version: 7.7
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Lukáš Czerner
QA Contact: Boyang Xue
URL:
Whiteboard:
: 1722761 (view as bug list)
Depends On:
Blocks: 1655750 1702415 1720435
TreeView+ depends on / blocked
 
Reported: 2019-06-16 11:15 UTC by Yuval Turgeman
Modified: 2020-12-31 06:17 UTC (History)
15 users (show)

Fixed In Version: e2fsprogs-1.42.9-16.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:01:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2176 0 None None None 2019-08-06 13:02:05 UTC

Description Yuval Turgeman 2019-06-16 11:15:12 UTC 
Description of problem:
When running e2fsck on an LV that needed a fix, fsck segfaults on exit when it tries to free its context.

Version-Release number of selected component (if applicable):
e2fsprogs-1.42.9-15.el7.x86_64

How reproducible:
The first fsck run on a fs that is not clean

Steps to Reproduce:
1. Force fsck on a system that is not clean

Actual results:

# e2fsck -v -y -f /dev/rhvh/rhvh-4.3.5.1-0.20190613.0
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

       55853 inodes used (13.85%, out of 403200)
          25 non-contiguous files (0.0%)
          56 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 54348
      631430 blocks used (39.15%, out of 1612800)
           0 bad blocks
           1 large file

       46720 regular files
        7512 directories
           0 character device files
           0 block device files
           0 fifos
       15261 links
        1612 symbolic links (1497 fast symbolic links)
           0 sockets
------------
       71105 files
Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
e2fsck[0x427671]
/lib64/libc.so.6(+0x363f0)[0x7f9957cab3f0]
/lib64/libext2fs.so.2(ext2fs_free_dblist+0x1d)[0x7f99588b055d]
e2fsck(e2fsck_reset_context+0x108)[0x40dc58]
e2fsck(e2fsck_free_context+0x26)[0x40def6]
e2fsck(main+0x1b6e)[0x40af5e]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f9957c97545]
e2fsck[0x40be7a]

Expected results:
fsck should fix the system and exit nicely

Additional info:
This is probably happening because ctx->fs (or ctx->fs->dblist) is not set to NULL, so fsck fixes the fs and segfaults on exit.  If we re-run fsck on that filesystem, it finishes correctly.
Comment 22 Lukáš Czerner 2019-07-01 08:33:25 UTC 
*** Bug 1722761 has been marked as a duplicate of this bug. ***
Comment 24 errata-xmlrpc 2019-08-06 13:01:21 UTC 
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://access.redhat.com/errata/RHBA-2019:2176
Note You need to log in before you can comment on or make changes to this bug.