This bug was fixed in the package linux - 3.13.0-135.184
---------------
linux (3.13.0-135.184) trusty; urgency=low
* linux: 3.13.0-135.184 -proposed tracker (LP: #1724500)
* Trusty NVMe boot fails on some systems (LP: #1720867)
- NVMe: RCU protected access to io queues
- NVMe: IOCTL path RCU protect queue access
- powerpc/mm: fix ".__node_distance" undefined
- NVMe: per-cpu io queues
- nvme: Use pci_enable_msi_range() and pci_enable_msix_range()
- NVMe: make setup work for devices that don't do INTx
- NVMe: Always use MSI/MSI-x interrupts
linux (3.13.0-134.183) trusty; urgency=low
* linux: 3.13.0-134.183 -proposed tracker (LP: #1722335)
[ Thadeu Lima de Souza Cascardo ]
* CVE-2017-10661
- timerfd: Protect the might cancel mechanism proper
* CVE-2017-10662
- f2fs: sanity check segment count
* CVE-2017-10663
- f2fs: sanity check checkpoint segno and blkoff
* CVE-2017-14340
- xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present
* CVE-2017-10911
- xen-blkback: don't leak stack data via response ring
* CVE-2017-11176
- mqueue: fix a use-after-free in sys_mq_notify()
* CVE-2016-8632
- tipc: check minimum bearer MTU
-- Thadeu Lima de Souza Cascardo <[email protected]> Wed, 18 Oct
2017 07:09:04 -0200
** Changed in: linux (Ubuntu Trusty)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-8632
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10661
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10662
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10663
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10911
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-11176
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-14340
** Changed in: linux (Ubuntu Trusty)
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/1720867
Title:
Trusty NVMe boot fails on some systems
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Released
Bug description:
Trusty linux (3.13) fails to boot on some NVMe-based cloud instance
types.
[Impact]
* Ubuntu trusty images can't be used on some NVMe-based cloud
instance types.
* Mainline commit a522905 "NVMe: Always use MSI/MSI-x interrupts"
fixes the issue; application of this to 3.13 requires a set of
prerequisite patches, and a minor backport.
a522905 NVMe: Always use MSI/MSI-x interrupts
e32efbf NVMe: make setup work for devices that don't do INTx
be577fa nvme: Use pci_enable_msi_range() and pci_enable_msix_range()
42f6142 NVMe: per-cpu io queues
4f5099a NVMe: IOCTL path RCU protect queue access
5a92e70 NVMe: RCU protected access to io queues
[Test Case]
* Verify that a trusty-based image can boot on the affected instance
type.
[Regression Potential]
* This change set affects all users of the NVMe driver, so regression
potential is moderate to high. Additional soak testing may be
warranted before merging this patch set.
* The patched NVMe driver has been exercised by Dan Streetman, and
given the thumbs-up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720867/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
