This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See for documentation how
to enable and use -proposed. Thank you!

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13 ADT test
  failure with linux 4.9.0-12.13)

Status in Linux:
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

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:

  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.

  Reported-by: Colin Ian King <>
  Signed-off-by: Theodore Ts'o <>

  == 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


  Testing failed on:

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to