This bug was fixed in the package linux - 4.8.0-49.52
---
linux (4.8.0-49.52) yakkety; urgency=low
* linux: 4.8.0-49.52 -proposed tracker (LP: #1684427)
* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move
This bug was fixed in the package linux - 4.4.0-75.96
---
linux (4.4.0-75.96) xenial; urgency=low
* linux: 4.4.0-75.96 -proposed tracker (LP: #1684441)
* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move
This bug was fixed in the package linux - 3.13.0-117.164
---
linux (3.13.0-117.164) trusty; urgency=low
* linux: 3.13.0-117.164 -proposed tracker (LP: #1680733)
* CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it
* CVE-2017-5986
- sctp:
tested on Trusty with the -proposed 3.13.0-117-generic and
4.4.0-74-generic #95~14.04.1 HWE kernel, ran 16 xattr stressors for 5
minutes, no failure, passed.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are
tested on Yakkety with the -proposed 4.8.0-48-geneirc kernel, ran 16
xattr stressors for 5 minutes, no failure, passed.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
tested on xenial with the -proposed 4.4.0-74-generic kernel, ran 16
xattr stressors for 5 minutes, no failure, passed.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
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
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-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag
This bug was fixed in the package linux - 4.10.0-19.21
---
linux (4.10.0-19.21) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1680535
* ADT regressions caused by "audit: fix auditd/kernel connection state
tracking" (LP: #1680532)
- SAUCE: Revert
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658633
Title:
stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658633
Title:
stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658633
Title:
stress_smoke_test passing and exiting rc=9 (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
** 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:
+
Still an issue with 4.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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)
To
** Bug watch added: Linux Kernel Bug Tracker #193661
http://bugzilla.kernel.org/show_bug.cgi?id=193661
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=193661
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
OK, looks like a need a cleanly formatted ext4 file system before *each*
bisect otherwise I'm picking up xattr corruption from previous bisects.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658633
Issue still in 4.10-rc6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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)
To
Only breaks with ext4, i386 and > 1 cpu. Can't break amd64 or
uniprocessor configs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658633
Title:
stress_smoke_test passing and exiting rc=9 (linux
Does not break on xfs, so looks like an ext4 issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
Right, I think this occurs when ext4 goes read-only. A simple way to
reproduce this on i386 systems with that kernel is:
sudo stress-ng --sockpair 10 && sudo stress-ng --xattr 10
xattr test causes ext4 to detect xattr issues and the file system gets
remounted r/o, and we no longer can log the
It is more probable that the mlock (or mmap) or later tests broke the
test and we are just seeing the last PASSED tests that got fflushed to
stdout before the ADT framework terminated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
24 matches
Mail list logo
