group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1658633@xxxxxxxxxxxxxxxxxx>]

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 <kleber.souza@xxxxxxxxxxxxx>  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 नेपाली
भाषा समायोजकहरुको समूह, 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:
  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 <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