group.of.nepali.translators team mailing list archive

Thread
Date
[Bug 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1650635@xxxxxxxxxxxxxxxxxx>
Date: Tue, 10 Jan 2017 14:11:15 -0000
Reply-to: Bug 1650635 <1650635@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
This bug was fixed in the package linux - 4.4.0-59.80

---------------
linux (4.4.0-59.80) xenial; urgency=low

  [ John Donnelly ]

  * Release Tracking Bug
    - LP: #1654282

  * [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails (LP: #1651602)
    - (fix) nvme: only require 1 interrupt vector, not 2+

linux (4.4.0-58.79) xenial; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1651402

  * Support ACPI probe for IIO sensor drivers from ST Micro (LP: #1650123)
    - SAUCE: iio: st_sensors: match sensors using ACPI handle
    - SAUCE: iio: st_accel: Support sensor i2c probe using acpi
    - SAUCE: iio: st_pressure: Support i2c probe using acpi
    - [Config] CONFIG_HTS221=m, CONFIG_HTS221_I2C=m, CONFIG_HTS221_SPI=m

  * Fix channel data parsing in ST Micro sensor IIO drivers (LP: #1650189)
    - SAUCE: iio: common: st_sensors: fix channel data parsing

  * ST Micro lng2dm 3-axis "femto" accelerometer support (LP: #1650112)
    - SAUCE: iio: st-accel: add support for lis2dh12
    - SAUCE: iio: st_sensors: support active-low interrupts
    - SAUCE: iio: accel: Add support for the h3lis331dl accelerometer
    - SAUCE: iio: st_sensors: verify interrupt event to status
    - SAUCE: iio: st_sensors: support open drain mode
    - SAUCE: iio:st_sensors: fix power regulator usage
    - SAUCE: iio: st_sensors: switch to a threaded interrupt
    - SAUCE: iio: accel: st_accel: Add lis3l02dq support
    - SAUCE: iio: st_sensors: fix scale configuration for h3lis331dl
    - SAUCE: iio: accel: st_accel: add support to lng2dm
    - SAUCE: iio: accel: st_accel: inline per-sensor data
    - SAUCE: Documentation: dt: iio: accel: add lng2dm sensor device binding

  * ST Micro hts221 relative humidity sensor support (LP: #1650116)
    - SAUCE: iio: humidity: add support to hts221 rh/temp combo device
    - SAUCE: Documentation: dt: iio: humidity: add hts221 sensor device binding
    - SAUCE: iio: humidity: remove
    - SAUCE: iio: humidity: Support acpi probe for hts211

  * crypto : tolerate new crypto hardware for z Systems (LP: #1644557)
    - s390/zcrypt: Introduce CEX6 toleration

  * Acer, Inc ID 5986:055a is useless after 14.04.2 installed. (LP: #1433906)
    - uvcvideo: uvc_scan_fallback() for webcams with broken chain

  * vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
    (LP: #1650635)
    - vmxnet3: segCnt can be 1 for LRO packets

  * system freeze when swapping to encrypted swap partition (LP: #1647400)
    - mm, oom: rework oom detection
    - mm: throttle on IO only when there are too many dirty and writeback pages

  * Kernel Fixes to get TCMU File Backed Optical to work (LP: #1646204)
    - target/user: Use sense_reason_t in tcmu_queue_cmd_ring
    - target/user: Return an error if cmd data size is too large
    - target/user: Fix comments to not refer to data ring
    - SAUCE: (no-up) target/user: Fix use-after-free of tcmu_cmds if they are
      expired

  * CVE-2016-9756
    - KVM: x86: drop error recovery in em_jmp_far and em_ret_far

  * Dell Precision 5520 & 3520 freezes at login screent (LP: #1650054)
    - ACPI / blacklist: add _REV quirks for Dell Precision 5520 and 3520

  * CVE-2016-9794
    - ALSA: pcm : Call kill_fasync() in stream lock

  * Allow fuse user namespace mounts by default in xenial (LP: #1634964)
    - (namespace) mnt: Move the FS_USERNS_MOUNT check into sget_userns
    - (namespace) Revert "UBUNTU: SAUCE: fs: Refuse uid/gid changes which don't
      map into s_user_ns"
    - (namespace) fs: Refuse uid/gid changes which don't map into s_user_ns
    - (namespace) Revert "UBUNTU: SAUCE: fs: Update posix_acl support to handle
      user namespace mounts"
    - (namespace) vfs: Verify acls are valid within superblock's s_user_ns.
    - SAUCE: (namespace) posix_acl: Export posix_acl_fix_xattr_userns() to modules
    - SAUCE: (namespace) fuse: Translate ids in posix acl xattrs
    - (namespace) vfs: Don't modify inodes with a uid or gid unknown to the vfs
    - (namespace) vfs: Don't create inodes with a uid or gid unknown to the vfs
    - (namespace) Revert "UBUNTU: SAUCE: quota: Require that qids passed to
      dqget() be valid and map into s_user_ns"
    - (namespace) Revert "UBUNTU: SAUCE: quota: Convert ids relative to s_user_ns"
    - (namespace) quota: Ensure qids map to the filesystem
    - (namespace) quota: Handle quota data stored in s_user_ns in quota_setxquota
    - (namespace) dquot: For now explicitly don't support filesystems outside of
      init_user_ns
    - (namespace) Revert "UBUNTU: SAUCE: ima/evm: Allow root in s_user_ns to set
      xattrs"
    - SAUCE: (namespace) security/integrity: Harden against malformed xattrs
    - (namespace) Revert "UBUNTU: SAUCE: fs: Allow superblock owner to change
      ownership of inodes with unmappable ids"
    - SAUCE: (namespace) fs: Allow superblock owner to change ownership of inodes
    - (namespace) Revert "UBUNTU: SAUCE: fs: Don't remove suid for CAP_FSETID in
      s_user_ns"
    - SAUCE: (namespace) fs: Don't remove suid for CAP_FSETID for userns root
    - SAUCE: (namespace) fuse: Allow user namespace mounts by default

  * Boot crash in xen_send_IPI_one (LP: #1649821)
    - xen/qspinlock: Don't kick CPU if IRQ is not initialized

  * linux: Staging modules should be unsigned (LP: #1642368)
    - [Debian] Suppress module signing for staging drivers
    - SAUCE: Add rtl drivers to signature inclusion list

  * Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]
    (LP: #1648279)
    - ACPI / blacklist: Make Dell Latitude 3350 ethernet work

  * CVE-2016-9793
    - net: avoid signed overflows for SO_{SND|RCV}BUFFORCE

  * [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04, and
    15.10 (LP: #1400319)
    - Drivers: hv: avoid vfree() on crash

  * [Hyper-V] netvsc: fix incorrect receive checksum offloading (LP: #1636656)
    - netvsc: fix incorrect receive checksum offloading

 -- John Donnelly <john.donnelly@xxxxxxxxxxxxx>  Thu, 05 Jan 2017
12:49:16 +0000

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

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

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

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

-- 
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/1650635

Title:
  vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  It has been brought to my attention that a Trusty Vmware Virtual
  Machine running kernel v4.4.0-36 crashed with the following stacktrace
  :

  PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!"
  ...
  #0 [ffff88042d683aa0] machine_kexec at ffffffff8105987c
  #1 [ffff88042d683af8] crash_kexec at ffffffff81105d23
  #2 [ffff88042d683bc0] oops_end at ffffffff81030a79
  #3 [ffff88042d683be8] die at ffffffff81030f7b
  #4 [ffff88042d683c18] do_trap at ffffffff8102e04d
  #5 [ffff88042d683c68] do_error_trap at ffffffff8102e5a7
  #6 [ffff88042d683d20] do_invalid_op at ffffffff8102e840
  #7 [ffff88042d683d30] invalid_op at ffffffff817f900e
  [exception RIP: vmxnet3_rq_rx_complete+3016]
  RIP: ffffffffc004e448 RSP: ffff88042d683de8 RFLAGS: 00010246
  RAX: 0000000000000001 RBX: ffff880424099668 RCX: 0000000000000000
  RDX: 00000000000005f2 RSI: 00000000000005f2 RDI: ffff88042a61f400
  RBP: ffff88042d683e50 R8: 0000000000000000 R9: 0000000000000000
  R10: ffff88042902b470 R11: ffff8804293406a8 R12: ffff880424098840
  R13: ffff880424099580 R14: ffff88042a61ec00 R15: ffff88042933ae00
  ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
  #8 [ffff88042d683de0] vmxnet3_rq_rx_complete at ffffffffc004dcfa [vmxnet3]
  #9 [ffff88042d683e58] vmxnet3_poll_rx_only at ffffffffc004e60a [vmxnet3]
  #10 [ffff88042d683e90] net_rx_action at ffffffff816f3544
  #11 [ffff88042d683f00] __do_softirq at ffffffff81081e7d
  #12 [ffff88042d683f68] irq_exit at ffffffff81082255
  #13 [ffff88042d683f78] do_IRQ at ffffffff817f9ee6
  --- <IRQ stack> ---
  #14 [ffff880426c73f30] ret_from_intr at ffffffff817f7fc2
  [exception RIP: unknown or invalid address]
  RIP: fffffffffffffffb RSP: 00007fe17e59bf48 RFLAGS: 00000001
  RAX: 00007fe18564ed58 RBX: 00007fe2064ce848 RCX: 00007fe185612d60
  RDX: 00007fe20b47eb30 RSI: 00007fe185640d38 RDI: 00007fe18564ed50
  RBP: ffffffff817f7fe5 R8: 00007fe185100068 R9: 0000000000037ce0
  R10: 0000000000134ad8 R11: 00007fe17e4b7028 R12: 00007fe185100068
  R13: 00007fe185632380 R14: 0000000000000000 R15: ffffffff81003a64
  ORIG_RAX: 0000000000000001 CS: 7fe185640d38 SS: ffffffffffffff91
  bt: WARNING: possibly bogus exception frame
  RIP: 00000000004e92bb RSP: 00007fe20b47ea40 RFLAGS: 00000283
  RAX: 0000000000000001 RBX: 00007fe18564ed58 RCX: fffffffffffffffb
  RDX: 00007fe185640d38 RSI: 0000000000000001 RDI: 00007fe17e59bf48
  RBP: 00007fe185100068 R8: 00007fe18564ed50 R9: 00007fe185640d38
  R10: 00007fe20b47eb30 R11: 00007fe185612d60 R12: 0000000000037ce0
  R13: 0000000000134ad8 R14: 00007fe17e4b7028 R15: 00007fe2064ce848
  ORIG_RAX: ffffffffffffff91 CS: 0033 SS: 002b

  [Test Case]

   * There is no real reproducer, the problem occurred randomly if
  SegCnt == 1 on a Trusty VMware Virtual Machine using Xenial kernel
  with LRO enabled in the VMware environment.

  [Regression Potential]

   * none expected
   * Commit can be found in upstream linux stable
   * Yakkety and Zesty kernel has the patch already

  [Other Info]

   * Upstream commit :
     5021953 vmxnet3: segCnt can be 1 for LRO packets

  [Original Description]

  It has been brought to my attention that a Trusty Vmware Virtual
  Machine running kernel v4.4.0-36 crashed with the following stacktrace
  :

  PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!"
  ...
  #0 [ffff88042d683aa0] machine_kexec at ffffffff8105987c
  #1 [ffff88042d683af8] crash_kexec at ffffffff81105d23
  #2 [ffff88042d683bc0] oops_end at ffffffff81030a79
  #3 [ffff88042d683be8] die at ffffffff81030f7b
  #4 [ffff88042d683c18] do_trap at ffffffff8102e04d
  #5 [ffff88042d683c68] do_error_trap at ffffffff8102e5a7
  #6 [ffff88042d683d20] do_invalid_op at ffffffff8102e840
  #7 [ffff88042d683d30] invalid_op at ffffffff817f900e
  [exception RIP: vmxnet3_rq_rx_complete+3016]
  RIP: ffffffffc004e448 RSP: ffff88042d683de8 RFLAGS: 00010246
  RAX: 0000000000000001 RBX: ffff880424099668 RCX: 0000000000000000
  RDX: 00000000000005f2 RSI: 00000000000005f2 RDI: ffff88042a61f400
  RBP: ffff88042d683e50 R8: 0000000000000000 R9: 0000000000000000
  R10: ffff88042902b470 R11: ffff8804293406a8 R12: ffff880424098840
  R13: ffff880424099580 R14: ffff88042a61ec00 R15: ffff88042933ae00
  ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
  #8 [ffff88042d683de0] vmxnet3_rq_rx_complete at ffffffffc004dcfa [vmxnet3]
  #9 [ffff88042d683e58] vmxnet3_poll_rx_only at ffffffffc004e60a [vmxnet3]
  #10 [ffff88042d683e90] net_rx_action at ffffffff816f3544
  #11 [ffff88042d683f00] __do_softirq at ffffffff81081e7d
  #12 [ffff88042d683f68] irq_exit at ffffffff81082255
  #13 [ffff88042d683f78] do_IRQ at ffffffff817f9ee6
  --- <IRQ stack> ---
  #14 [ffff880426c73f30] ret_from_intr at ffffffff817f7fc2
  [exception RIP: unknown or invalid address]
  RIP: fffffffffffffffb RSP: 00007fe17e59bf48 RFLAGS: 00000001
  RAX: 00007fe18564ed58 RBX: 00007fe2064ce848 RCX: 00007fe185612d60
  RDX: 00007fe20b47eb30 RSI: 00007fe185640d38 RDI: 00007fe18564ed50
  RBP: ffffffff817f7fe5 R8: 00007fe185100068 R9: 0000000000037ce0
  R10: 0000000000134ad8 R11: 00007fe17e4b7028 R12: 00007fe185100068
  R13: 00007fe185632380 R14: 0000000000000000 R15: ffffffff81003a64
  ORIG_RAX: 0000000000000001 CS: 7fe185640d38 SS: ffffffffffffff91
  bt: WARNING: possibly bogus exception frame
  RIP: 00000000004e92bb RSP: 00007fe20b47ea40 RFLAGS: 00000283
  RAX: 0000000000000001 RBX: 00007fe18564ed58 RCX: fffffffffffffffb
  RDX: 00007fe185640d38 RSI: 0000000000000001 RDI: 00007fe17e59bf48
  RBP: 00007fe185100068 R8: 00007fe18564ed50 R9: 00007fe185640d38
  R10: 00007fe20b47eb30 R11: 00007fe185612d60 R12: 0000000000037ce0
  R13: 0000000000134ad8 R14: 00007fe17e4b7028 R15: 00007fe2064ce848
  ORIG_RAX: ffffffffffffff91 CS: 0033 SS: 002b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635/+subscriptions