** Description changed: + == 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.k...@canonical.com> + Signed-off-by: Theodore Ts'o <ty...@mit.edu> + Cc: sta...@vger.kernel.org + + == 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 + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/l/linux/20170122_110123_770b2@/log.gz
** Description changed: - == SRU Request [ Trusty, Xenial, Yakkey ] + Zesty + == 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.k...@canonical.com> Signed-off-by: Theodore Ts'o <ty...@mit.edu> Cc: sta...@vger.kernel.org == 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. 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 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.k...@canonical.com> Signed-off-by: Theodore Ts'o <ty...@mit.edu> Cc: sta...@vger.kernel.org == 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
