Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
When fsck.gfs2 resolves duplicate block references, if all block references are found to be invalid (no valid references are found), its reference list becomes empty.
Some code in pass1b improperly tried to access references on the empty list. As a result, fsck.gfs2 would end abnormally with a segmentation fault. Code was added to pass1b to check for the list being empty. As a result, the segmentation fault no longer occurs and fsck.gfs2 proceeds normally.
DescriptionRobert Peterson
2011-02-21 14:19:55 UTC
+++ This bug was initially created as a clone of Bug #679076 +++
Cloned for a RHEL6 crosswrite fix.
Description of problem:
While recently analyzing a customer's gfs2 metadata, I ran
fsck.gfs2 and it segfaulted in pass1b. I tracked down the
problem, and this bug is to track the problem and its fix.
Version-Release number of selected component (if applicable):
RHEL57
How reproducible:
Unknown
Steps to Reproduce:
1. Restore customer metadata
2. fsck.gfs2 -y /dev/device
3.
Actual results:
Segfault in pass1b
Expected results:
fsck.gfs2 should run to completion.
Additional info:
Patch available
--- Additional comment from rpeterso on 2011-02-21 09:15:25 EST ---
Created attachment 479925[details]
Patch to fix the problem
The problem occurred when there were duplicate block
references in a dinode but all references in the duplicate
list are eventually deleted due to other corruption.
The fix is an additional check whether the list is empty.
--- Additional comment from rpeterso on 2011-02-21 09:16:28 EST ---
Requesting ack flags for 5.7.
I pushed the patch to the master branch of the gfs2-util
git repo. I guess I'll have to wait to push it into the
RHEL6 branch of cluster.git until 6.1 branches from RHEL6,
unless management wants to squeeze it in.
Since the RHEL6 branch is now open for business, I pushed the
patch to it for inclusion into 6.2. I tested it on system
gfs-i24c-01. Changing status to POST until it gets built.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When fsck.gfs2 resolves duplicate block references, if all block references are found to be invalid (no valid references are found), its reference list becomes empty.
Some code in pass1b improperly tried to access references on the empty list. As a result, fsck.gfs2 would end abnormally with a segmentation fault. Code was added to pass1b to check for the list being empty. As a result, the segmentation fault no longer occurs and fsck.gfs2 proceeds normally.
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.
http://rhn.redhat.com/errata/RHBA-2011-1516.html