stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Unknown
|
Unknown
|
|||
linux (Ubuntu) |
Fix Released
|
High
|
Colin Ian King | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
== SRU Request [ Trusty, Xenial, Yakkey ] + Zesty ==
When running the stress-ng --xattr stressor with several instances of the stressor on ext4 we can trip an xattr bug in the ext4 file system.
== Fix ==
Upstream commit: https:/
ext4: lock the xattr block before checksuming it
We must lock the xattr block before calculating or verifying the
checksum in order to avoid spurious checksum failures.
https:/
Reported-by: Colin Ian King <email address hidden>
Signed-off-by: Theodore Ts'o <email address hidden>
Cc: <email address hidden>
== Test case ==
Fire up an x86 VM with 8 or more CPUs in the instance, run:
stress-ng --xattr 0 -t 60 -v
Without the fix, the file system will report broken xattrs and the file system will go read-only.
With the fix, it runs without fault.
== Regression Potential ==
This changes the checksumming in the ext4 xattr so it only touches the ext4 xattr part of the file system. Risk is therefore contained in the xattr handling on ext4. Tested with stress-ng and the generic file system tests without any regressions, so risk is limited and small.
-------
Testing failed on:
ppc64el: https:/
tags: | added: kernel-adt-failure |
Changed in linux (Ubuntu): | |
assignee: | nobody → Colin Ian King (colin-king) |
importance: | Undecided → High |
status: | Confirmed → In Progress |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Trusty): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Xenial): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Yakkety): | |
status: | New → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1658633
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.