Activity log for bug #1658633

Date Who What changed Old value New value Message
2017-01-23 09:53:51 Andy Whitcroft bug added bug
2017-01-23 10:00:06 Andy Whitcroft tags kernel-adt-failure
2017-01-23 10:00:15 Brad Figg linux (Ubuntu): status New Incomplete
2017-01-23 10:00:34 Andy Whitcroft description Testing failed on: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/l/linux/20170122_110123_770b2@/log.gz
2017-01-23 10:02:46 Andy Whitcroft summary linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13 stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13 ADT test failure with linux 4.9.0-12.13)
2017-01-23 10:04:08 Andy Whitcroft linux (Ubuntu): status Incomplete Confirmed
2017-01-23 10:17:38 Colin Ian King linux (Ubuntu): assignee Colin Ian King (colin-king)
2017-01-23 10:17:40 Colin Ian King linux (Ubuntu): importance Undecided High
2017-01-23 10:17:43 Colin Ian King linux (Ubuntu): status Confirmed In Progress
2017-01-30 16:06:42 Colin Ian King bug watch added http://bugzilla.kernel.org/show_bug.cgi?id=193661
2017-01-30 16:06:42 Colin Ian King bug task added linux
2017-03-27 11:18:56 Colin Ian King description Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/l/linux/20170122_110123_770b2@/log.gz == 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@canonical.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: stable@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
2017-03-27 11:19:07 Colin Ian King 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@canonical.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: stable@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 == 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@canonical.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: stable@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
2017-03-27 14:51:27 Stefan Bader nominated for series Ubuntu Yakkety
2017-03-27 14:51:27 Stefan Bader bug task added linux (Ubuntu Yakkety)
2017-03-27 14:54:57 Stefan Bader nominated for series Ubuntu Xenial
2017-03-27 14:54:57 Stefan Bader bug task added linux (Ubuntu Xenial)
2017-03-27 14:54:57 Stefan Bader nominated for series Ubuntu Trusty
2017-03-27 14:54:57 Stefan Bader bug task added linux (Ubuntu Trusty)
2017-03-29 11:21:53 Thadeu Lima de Souza Cascardo linux (Ubuntu Trusty): status New Fix Committed
2017-03-29 11:30:04 Thadeu Lima de Souza Cascardo linux (Ubuntu Xenial): status New Fix Committed
2017-03-29 12:02:02 Thadeu Lima de Souza Cascardo linux (Ubuntu Yakkety): status New Fix Committed
2017-04-08 01:48:20 Launchpad Janitor linux (Ubuntu): status In Progress Fix Released
2017-04-08 01:48:20 Launchpad Janitor cve linked 2017-7308
2017-04-13 16:13:01 Kleber Sacilotto de Souza tags kernel-adt-failure kernel-adt-failure verification-needed-trusty
2017-04-13 16:14:22 Kleber Sacilotto de Souza tags kernel-adt-failure verification-needed-trusty kernel-adt-failure verification-needed-trusty verification-needed-xenial
2017-04-13 16:15:52 Kleber Sacilotto de Souza tags kernel-adt-failure verification-needed-trusty verification-needed-xenial kernel-adt-failure verification-needed-trusty verification-needed-xenial verification-needed-yakkety
2017-04-13 16:51:56 Colin Ian King tags kernel-adt-failure verification-needed-trusty verification-needed-xenial verification-needed-yakkety kernel-adt-failure verification-done-xenial verification-needed-trusty verification-needed-yakkety
2017-04-13 17:03:48 Colin Ian King tags kernel-adt-failure verification-done-xenial verification-needed-trusty verification-needed-yakkety kernel-adt-failure verification-done-xenial verification-done-yakkety verification-needed-trusty
2017-04-13 17:58:33 Colin Ian King tags kernel-adt-failure verification-done-xenial verification-done-yakkety verification-needed-trusty kernel-adt-failure verification-done-trusty verification-done-xenial verification-done-yakkety
2017-04-24 14:07:40 Launchpad Janitor linux (Ubuntu Trusty): status Fix Committed Fix Released
2017-04-24 14:07:40 Launchpad Janitor cve linked 2017-5986
2017-04-24 14:07:40 Launchpad Janitor cve linked 2017-6353
2017-04-24 14:09:16 Launchpad Janitor linux (Ubuntu Xenial): status Fix Committed Fix Released
2017-04-24 14:11:40 Launchpad Janitor linux (Ubuntu Yakkety): status Fix Committed Fix Released