kernel-packages team mailing list archive

[Launchpad Bug Tracker <1396470@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package linux - 3.18.0-8.9

---------------
linux (3.18.0-8.9) vivid; urgency=low

  [ Leann Ogasawara ]

  * Release Tracking Bug
    - LP: #1407692
  * rebase to v3.18.1
  * ubuntu: AUFS -- Resolve build failure union has no member named
    'd_child'

  [ Upstream Kernel Changes ]

  * arm64: optimized copy_to_user and copy_from_user assembly code
    - LP: #1400349
  * x86, kvm: Clear paravirt_enabled on KVM guests for espfix32's benefit
    - LP: #1400314
    - CVE-2014-8134
  * rebase to v3.18.1
 -- Leann Ogasawara <leann.ogasawara@xxxxxxxxxxxxx>   Mon, 05 Jan 2015 09:12:32 -0800

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

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

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

Title:
  please enable CONFIG_VIRTIO_MMIO on armmp

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Invalid
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  Degraded performance during network and disk activity in a kvm guest.

  [Test case]
  Try booting a vm and do some disk/net activity with and without this driver.

  [Regression potential]
  In case of regressions, it will just hit people using kvm on 32bit armhf hardware (the lpae variant in particular): we already had this driver on in the past, it's on by default on every arch, it's widely used and upstream is very active - i say it's a low potential regression.

  --
  Hi,

  The current armmp (linux-
  image-3.16.0-26-generic_3.16.0-26.34_armhf.deb) could have virtio-mmio
  enabled for faster vm guests. Currenlty it seems to have:

  CONFIG_NET_9P_VIRTIO=m
  CONFIG_VIRTIO_BLK=y
  CONFIG_SCSI_VIRTIO=m
  CONFIG_VIRTIO_NET=y
  CONFIG_CAIF_VIRTIO=m
  CONFIG_VIRTIO_CONSOLE=y
  CONFIG_HW_RANDOM_VIRTIO=m
  CONFIG_VIRTIO=y
  CONFIG_VIRTIO_PCI=y
  # CONFIG_VIRTIO_BALLOON is not set
  # CONFIG_VIRTIO_MMIO is not set

  Now using virtio net and block is not possible, and you have to revert
  to emulated devices.

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