subject:"\[Kernel\-packages\] \[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\)"

[Kernel-packages] [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)

2017-04-24 Thread Launchpad Bug Tracker

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: avoid BUG_ON on sctp_wait_for_sndbuf

  * Update ENA driver to 1.1.2 from net-next (LP: #1664312)
- net: ena: Remove unnecessary pci_set_drvdata()
- net: ena: Fix error return code in ena_device_init()
- net: ena: change the return type of ena_set_push_mode() to be void.
- net: ena: use setup_timer() and mod_timer()
- net/ena: remove ntuple filter support from device feature list
- net/ena: fix queues number calculation
- net/ena: fix ethtool RSS flow configuration
- net/ena: fix RSS default hash configuration
- net/ena: fix NULL dereference when removing the driver after device reset
  failed
- net/ena: refactor ena_get_stats64 to be atomic context safe
- net/ena: fix potential access to freed memory during device reset
- net/ena: use READ_ONCE to access completion descriptors
- net/ena: reduce the severity of ena printouts
- net/ena: change driver's default timeouts
- net/ena: change condition for host attribute configuration
- net/ena: update driver version to 1.1.2

  * [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20
bytes to a sockaddr (LP: #1668042)
- net/bonding: Enforce active-backup policy for IPoIB bonds

  * stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13 ADT test
failure with linux 4.9.0-12.13) (LP: #1658633)
- ext4: lock the xattr block before checksuming it

  * vmxnet3 LRO IPv6 performance issues (stalling TCP) (LP: #1605494)
- Driver: Vmxnet3: set CHECKSUM_UNNECESSARY for IPv6 packets

  * move aufs.ko from -extra to linux-image package (LP: #1673498)
- [config] aufs.ko moved to linux-image package

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: fix btrfs_compat_ioctl failures on non-compat ioctls

 -- Kleber Sacilotto de Souza   Thu, 06 Apr
2017 17:52:50 +0100

** Changed in: linux (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5986

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-6353

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-04-24 Thread Launchpad Bug Tracker

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 waiting for release to hv_utils_transport itself

linux (4.8.0-48.51) yakkety; urgency=low

  * linux: 4.8.0-48.51 -proposed tracker (LP: #1682034)

  * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
(LP: #1681893)
- Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.8.0-47.50) yakkety; urgency=low

  * linux: 4.8.0-47.50 -proposed tracker (LP: #1679678)

  * CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it

  * CVE-2017-5986
- sctp: avoid BUG_ON on sctp_wait_for_sndbuf

  * vfat: missing iso8859-1 charset (LP: #1677230)
- [Config] NLS_ISO8859_1=y

  * [Hyper-V] pci-hyperv: Use device serial number as PCI domain (LP: #1667527)
- net/mlx4_core: Use cq quota in SRIOV when creating completion EQs

  * Regression: KVM modules should be on main kernel package (LP: #1678099)
- [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

  * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
4.4.0-63.84~14.04.2 (LP: #1664912)
- SAUCE: apparmor: fix link auditing failure due to, uninitialized var

  * regession tests failing after stackprofile test is run (LP: #1661030)
- SAUCE: fix regression with domain change in complain mode

  * Permission denied and inconsistent behavior in complain mode with 'ip netns
list' command (LP: #1648903)
- SAUCE: fix regression with domain change in complain mode

  * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
from a unshared mount namespace (LP: #1656121)
- SAUCE: apparmor: null profiles should inherit parent control flags

  * apparmor refcount leak of profile namespace when removing profiles
(LP: #1660849)
- SAUCE: apparmor: fix ns ref count link when removing profiles from policy

  * tor in lxd: apparmor="DENIED" operation="change_onexec"
namespace="root//CONTAINERNAME_" profile="unconfined"
name="system_tor" (LP: #1648143)
- SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using 
stacked
  namespaces

  * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
- SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

  * apparmor  auditing denied access of special apparmor .null fi\ le
(LP: #1660836)
- SAUCE: apparmor: Don't audit denied access of special apparmor .null file

  * apparmor label leak when new label is unused (LP: #1660834)
- SAUCE: apparmor: fix label leak when new label is unused

  * apparmor reference count bug in label_merge_insert() (LP: #1660833)
- SAUCE: apparmor: fix reference count bug in label_merge_insert()

  * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
- SAUCE: apparmor: fix replacement race in reading rawdata

  * unix domain socket cross permission check failing with nested namespaces
(LP: #1660832)
- SAUCE: apparmor: fix cross ns perm of unix domain sockets

  * [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device
shutdown (LP: #1672785)
- Revert "net/mlx4_en: Avoid unregister_netdev at shutdown flow"
- net/mlx4_core: Avoid delays during VF driver device shutdown

  * Update ENA driver to 1.1.2 from net-next (LP: #1664312)
- net: ena: Remove unnecessary pci_set_drvdata()
- net: ena: Fix error return code in ena_device_init()
- net: ena: change the return type of ena_set_push_mode() to be void.
- net: ena: use setup_timer() and mod_timer()
- net/ena: remove ntuple filter support from device feature list
- net/ena: fix queues number calculation
- net/ena: fix ethtool RSS flow configuration
- net/ena: fix RSS default hash configuration
- net/ena: fix NULL dereference when removing the driver after device reset
  failed
- net/ena: refactor ena_get_stats64 to be atomic context safe
- net/ena: fix potential access to freed memory during device reset
- net/ena: use READ_ONCE to access completion descriptors
- net/ena: reduce the severity of ena printouts
- net/ena: change driver's default timeouts
- net/ena: change condition for host attribute configuration
- net/ena: update driver version to 1.1.2

  * ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and numa_foreign
wrong in numastat (LP: #1672953)
- mm: fix remote numa hits statistics
- mm: get rid of __GFP_OTHER_NODE

  * Using an NVMe drive causes huge power drain (LP: #1664602)
- nvme/scsi: Remove power management support
- nvme: Pass pointers, not dma addresses, to nvme_get/set_features()
- nvme: introduce struct nvme_request
- nvme: Add a quirk

[Kernel-packages] [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)

2017-04-24 Thread Launchpad Bug Tracker

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 waiting for release to hv_utils_transport itself

linux (4.4.0-74.95) xenial; urgency=low

  * linux: 4.4.0-74.95 -proposed tracker (LP: #1682041)

  * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
(LP: #1681893)
- Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.4.0-73.94) xenial; urgency=low

  * linux: 4.4.0-73.94 -proposed tracker (LP: #1680416)

  * CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it

  * vfat: missing iso8859-1 charset (LP: #1677230)
- [Config] NLS_ISO8859_1=y

  * Regression: KVM modules should be on main kernel package (LP: #1678099)
- [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

  * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
4.4.0-63.84~14.04.2 (LP: #1664912)
- SAUCE: apparmor: fix link auditing failure due to, uninitialized var

  * regession tests failing after stackprofile test is run (LP: #1661030)
- SAUCE: fix regression with domain change in complain mode

  * Permission denied and inconsistent behavior in complain mode with 'ip netns
list' command (LP: #1648903)
- SAUCE: fix regression with domain change in complain mode

  * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
from a unshared mount namespace (LP: #1656121)
- SAUCE: apparmor: null profiles should inherit parent control flags

  * apparmor refcount leak of profile namespace when removing profiles
(LP: #1660849)
- SAUCE: apparmor: fix ns ref count link when removing profiles from policy

  * tor in lxd: apparmor="DENIED" operation="change_onexec"
namespace="root//CONTAINERNAME_" profile="unconfined"
name="system_tor" (LP: #1648143)
- SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using 
stacked
  namespaces

  * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
- SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

  * apparmor  auditing denied access of special apparmor .null fi\ le
(LP: #1660836)
- SAUCE: apparmor: Don't audit denied access of special apparmor .null file

  * apparmor label leak when new label is unused (LP: #1660834)
- SAUCE: apparmor: fix label leak when new label is unused

  * apparmor reference count bug in label_merge_insert() (LP: #1660833)
- SAUCE: apparmor: fix reference count bug in label_merge_insert()

  * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
- SAUCE: apparmor: fix replacement race in reading rawdata

  * unix domain socket cross permission check failing with nested namespaces
(LP: #1660832)
- SAUCE: apparmor: fix cross ns perm of unix domain sockets

  * Xenial update to v4.4.59 stable release (LP: #1678960)
- xfrm: policy: init locks early
- virtio_balloon: init 1st buffer in stats vq
- pinctrl: qcom: Don't clear status bit on irq_unmask
- c6x/ptrace: Remove useless PTRACE_SETREGSET implementation
- h8300/ptrace: Fix incorrect register transfer count
- mips/ptrace: Preserve previous registers for short regset write
- sparc/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Provide default TXSTATUS for short NT_PRSTATUS
- metag/ptrace: Reject partial NT_METAG_RPIPE writes
- fscrypt: remove broken support for detecting keyring key revocation
- sched/rt: Add a missing rescheduling point
- Linux 4.4.59

  * Update ENA driver to 1.1.2 from net-next (LP: #1664312)
- net: ena: Remove unnecessary pci_set_drvdata()
- net: ena: Fix error return code in ena_device_init()
- net: ena: change the return type of ena_set_push_mode() to be void.
- net: ena: use setup_timer() and mod_timer()
- net/ena: remove ntuple filter support from device feature list
- net/ena: fix queues number calculation
- net/ena: fix ethtool RSS flow configuration
- net/ena: fix RSS default hash configuration
- net/ena: fix NULL dereference when removing the driver after device reset
  failed
- net/ena: refactor ena_get_stats64 to be atomic context safe
- net/ena: fix potential access to freed memory during device reset
- net/ena: use READ_ONCE to access completion descriptors
- net/ena: reduce the severity of ena printouts
- net/ena: change driver's default timeouts
- net/ena: change condition for host attribute configuration
- net/ena: update driver version to 1.1.2

  * Xenial update to v4.4.58 stable release (LP: #1677600)
- net/openvswitch: Set the ipv6 source tunnel key

[Kernel-packages] [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)

2017-04-13 Thread Colin Ian King

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 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:
  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:
  
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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-04-13 Thread Colin Ian King

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 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:
  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:
  
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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-04-13 Thread Colin Ian King

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 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:
  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:
  
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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-04-13 Thread Kleber Sacilotto de Souza

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 'verification-needed-xenial' to 'verification-failed-
xenial'.

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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-yakkety

-- 
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:
  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:
  
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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-04-13 Thread Kleber Sacilotto de Souza

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 'verification-needed-trusty' to 'verification-failed-
trusty'.

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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-xenial

-- 
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:
  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:
  
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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-04-13 Thread Kleber Sacilotto de Souza

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-
yakkety'.

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 https://wiki.ubuntu.com/Testing/EnableProposed 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.
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:
  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:
  
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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-04-07 Thread Launchpad Bug Tracker

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 "audit: fix auditd/kernel connection state tracking"

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs to update CONFIG_GENERIC_CSUM for ppc64el
  This cleans up behind a Kconfig change that went undetected.

linux (4.10.0-18.20) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1680168

  * smartpqi driver needed in initram disk and installer (LP: #1680156)
- UBUNU: [Config] Add smartpqi to d-i

linux (4.10.0-17.19) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1679718

  * Fix CVE-2017-7308 (LP: #1678009)
- net/packet: fix overflow in check for priv area size
- net/packet: fix overflow in check for tp_frame_nr
- net/packet: fix overflow in check for tp_reserve

  * apparmor: oops on boot if parameters set on grub command line (LP: #1678048)
- SAUCE: apparmor: fix parameters so that the permission test is bypassed 
at boot

  * apparmor: does not provide a way to detect policy updataes (LP: #1678032)
- SAUCE: apparmor: add policy revision file interface

  * apparmor does not make support of query data visible (LP: #1678023)
- SAUCE: apparmor: add label data availability to the feature set

  * apparmor query interface does not make supported query info available
(LP: #1678030)
- SAUCE: apparmor: add information about the query inteface to the feature 
set

  * change_profile incorrect when using namespaces with a compound stack
(LP: #1677959)
- SAUCE: apparmor: fix label parse for stacked labels

  * Zesty update to v4.10.8 stable release (LP: #1678930)
- xfrm: policy: init locks early
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder
- KVM: nVMX: Fix nested VPID vmx exec control
- KVM: x86: cleanup the page tracking SRCU instance
- virtio_balloon: init 1st buffer in stats vq
- pinctrl: qcom: Don't clear status bit on irq_unmask
- c6x/ptrace: Remove useless PTRACE_SETREGSET implementation
- h8300/ptrace: Fix incorrect register transfer count
- mips/ptrace: Preserve previous registers for short regset write
- sparc/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Provide default TXSTATUS for short NT_PRSTATUS
- metag/ptrace: Reject partial NT_METAG_RPIPE writes
- qla2xxx: Allow vref count to timeout on vport delete.
- sched/rt: Add a missing rescheduling point
- usb: musb: fix possible spinlock deadlock
- Linux 4.10.8

  * [Hyper-V] pci-hyperv: Use device serial number as PCI domain (LP: #1667527)
- net/mlx4_core: Use cq quota in SRIOV when creating completion EQs
- PCI: hv: Use device serial number as PCI domain

  * Miscellaneous Ubuntu changes
- [Config] flash-kernel should be a Breaks
- [Config] drop the info directory
- [Config] drop NOTES as obsolete
- [Config] drop changelog.historical as obsolete

linux (4.10.0-16.18) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1677697

  * [Feature] ISH (Intel Sensor Hub) support (LP: #1645521)
- iio: accel: hid-sensor-accel-3d: Add timestamp

  * Zesty update to v4.10.7 stable release (LP: #1677589)
- net/openvswitch: Set the ipv6 source tunnel key address attribute 
correctly
- net: bcmgenet: Do not suspend PHY if Wake-on-LAN is enabled
- net: properly release sk_frag.page
- amd-xgbe: Fix jumbo MTU processing on newer hardware
- openvswitch: Add missing case OVS_TUNNEL_KEY_ATTR_PAD
- net: unix: properly re-increment inflight counter of GC discarded 
candidates
- qmi_wwan: add Dell DW5811e
- net: vrf: Reset rt6i_idev in local dst after put
- net/mlx5: Add missing entries for set/query rate limit commands
- net/mlx5e: Use the proper UAPI values when offloading TC vlan actions
- net/mlx5: Increase number of max QPs in default profile
- net/mlx5e: Count GSO packets correctly
- net/mlx5e: Count LRO packets correctly
- ipv6: make sure to initialize sockc.tsflags before first use
- net: bcmgenet: remove bcmgenet_internal_phy_setup()
- ipv4: provide stronger user input validation in nl_fib_input()
- socket, bpf: fix sk_filter use after free in sk_clone_lock
- genetlink: fix counting regression on ctrl_dumpfamily()
- tcp: initialize icsk_ack.lrcvtime at session start time
- amd-xgbe: Fix the ECC-related bit position definitions
- net: solve a NAPI race
- HID: sony: Fix input device leak when connecting a DS4 twice using USB/BT
- Input: ALPS - fix V8+ protocol handling

[Kernel-packages] [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)

2017-03-29 Thread Thadeu Lima de Souza Cascardo

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Committed

-- 
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
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:
  
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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-03-29 Thread Thadeu Lima de Souza Cascardo

** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
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
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:
  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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-03-29 Thread Thadeu Lima de Souza Cascardo

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

-- 
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
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:
  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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-03-27 Thread Stefan Bader

** 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 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
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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-03-27 Thread Colin Ian King

** 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 
+ Signed-off-by: Theodore Ts'o 
+ 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 
  Signed-off-by: Theodore Ts'o 
  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 
  Signed-off-by: Theodore Ts'o 
  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

[Kernel-packages] [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)

2017-02-21 Thread Colin Ian King

Still an issue with 4.10

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

[Kernel-packages] [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)

2017-01-30 Thread Colin Ian King

** 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 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:
  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

[Kernel-packages] [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)

2017-01-30 Thread Colin Ian King

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 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 package in Ubuntu:
  In Progress

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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

[Kernel-packages] [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)

2017-01-30 Thread Colin Ian King

Issue still in 4.10-rc6

-- 
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 package in Ubuntu:
  In Progress

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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

[Kernel-packages] [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)

2017-01-30 Thread Colin Ian King

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 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 package in Ubuntu:
  In Progress

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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

[Kernel-packages] [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)

2017-01-30 Thread Colin Ian King

Does not break on xfs, so looks like an ext4 issue

-- 
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 package in Ubuntu:
  In Progress

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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

[Kernel-packages] [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)

2017-01-23 Thread Colin Ian King

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 stress-ng ADT test log.

-- 
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 package in Ubuntu:
  In Progress

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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

[Kernel-packages] [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)

2017-01-23 Thread Colin Ian King

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 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 package in Ubuntu:
  In Progress

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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

[Kernel-packages] [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)

2017-01-23 Thread Colin Ian King

** 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 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 package in Ubuntu:
  In Progress

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/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

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

[Kernel-packages] [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)

24 matches

Site Navigation

Mail list logo

Footer information