← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1658633] Re: stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)

 

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1658633

Title:
  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:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Yakkety:
  New

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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dac7a4b4b1f664934e8b713f529b629f67db313c

  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://bugzilla.kernel.org/show_bug.cgi?id=193661

  Reported-by: Colin Ian King <colin.king@xxxxxxxxxxxxx>
  Signed-off-by: Theodore Ts'o <tytso@xxxxxxx>
  Cc: stable@xxxxxxxxxxxxxxx

  == 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://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/l/linux/20170122_110123_770b2@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1658633/+subscriptions