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 847106 - ext2 tests hang while running fsfuzzer
Summary: ext2 tests hang while running fsfuzzer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Carlos Maiolino
QA Contact: Boyang Xue
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-09 17:55 UTC by Gurhan Ozen
Modified: 2017-03-21 12:19 UTC (History)
12 users (show)

Fixed In Version: kernel-2.6.32-662.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 12:19:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
dmesg (23.14 KB, application/octet-stream)
2012-08-09 17:55 UTC, Gurhan Ozen 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0817 0 normal SHIPPED_LIVE Moderate: kernel security, bug fix, and enhancement update 2017-03-21 13:06:51 UTC

Description Gurhan Ozen 2012-08-09 17:55:36 UTC 
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:
Comment 2 Kamil Dudka 2012-08-09 19:55:54 UTC 
This could be hardly a bug of the 'filesystem' package, switching to kernel...
Comment 3 RHEL 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.
Comment 7 Carlos Maiolino 2013-03-28 18:20:37 UTC 
Gurhan, do you have the kernel version where you reproduced it?

Were you able to reproduce it on any recent kernel?

Thanks.

--Carlos
Comment 12 Jeff Burke 2013-11-05 14:51:15 UTC 
Yes this issue still exists.
Comment 14 Eric Sandeen 2013-11-05 15:14:34 UTC 
It should also be possible to grab the problematic image out of fsfuzzer to reproduce elsewhere.
Comment 15 Carlos Maiolino 2013-11-05 15:55:17 UTC 
I could reproduce it on my local test system, don't worry about access to the test system or take the fsfuzzer image.
Comment 16 Jeff Burke 2014-02-17 18:29:08 UTC 
Carlos,
 Any updates on this issue? 

Thanks,
Jeff
Comment 17 Carlos Maiolino 2014-02-17 18:40:25 UTC 
Hi Jeff,

don't have news regarding this bug yet, sorry.
I'll update it as soon as I have something for it.

Cheers,
--Carlos
Comment 18 Steve Whitehouse 2015-11-27 16:15:44 UTC 
Carlos, do you need something more to progress this - are you able to resproduce it, or do you need some more information?
Comment 19 Carlos Maiolino 2015-12-07 10:41:27 UTC 
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.
Comment 23 Phillip Lougher 2016-10-07 21:20:18 UTC 
Patch(es) committed on kernel repository and kernel is undergoing testing
Comment 25 Phillip Lougher 2016-10-12 13:59:42 UTC 
Patch(es) available on kernel-2.6.32-662.el6
Comment 31 errata-xmlrpc 2017-03-21 12:19:53 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://rhn.redhat.com/errata/RHSA-2017-0817.html
Note You need to log in before you can comment on or make changes to this bug.