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.
Created attachment 603319[details]
dmesg
Description of problem:
When running fsfuzzer for ext2 testing, it hangs.
dmesg that has the stacktraces will be attached.
Version-Release number of selected component (if applicable):
rhel6
How reproducible:
Very
Steps to Reproduce:
1. Reserve a rhel6 machine and install /kernel/storage/fsfuzzer test and run ./fsfuzz ext2
2.
3.
Actual results:
Expected results:
Additional info:
This could be hardly a bug of the 'filesystem' package, switching to kernel...
Comment 3RHEL Program Management
2012-12-14 08:25:31 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Hi Steve,
no, I don't need anything by now. I believe I have already identified the bug, but, if I'm right, it also exists upstream. I'm testing now if I can reproduce it upstream.
the bug looks to happen only on filesystems with 1K blocks, and a corrupted inode makes the filesystem try to lock the superblock twice.
At a first glance, I thought the bug could only happen when the ext2_xattr_delete_inode() was trying to delete an inode where i_file_acl was 1, which would make the function lock the superblock buffer_head, instead of the inode's buffer_head itself, but that's not the case.
I'm using some instrumentation code to isolate the bug, since, my first possible fix didn't work as expected.
I believe whenever i_file_acl points to a superblock buffer, it will triggers the bug, but, next investigation/code instrumentation might give me better results.
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://rhn.redhat.com/errata/RHSA-2017-0817.html
Created attachment 603319 [details] dmesg Description of problem: When running fsfuzzer for ext2 testing, it hangs. dmesg that has the stacktraces will be attached. Version-Release number of selected component (if applicable): rhel6 How reproducible: Very Steps to Reproduce: 1. Reserve a rhel6 machine and install /kernel/storage/fsfuzzer test and run ./fsfuzz ext2 2. 3. Actual results: Expected results: Additional info: