Activity log for bug #1818854

Date Who What changed Old value New value Message
2019-03-06 15:19:22 bugproxy bug added bug
2019-03-06 15:19:27 bugproxy tags architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804
2019-03-06 15:19:28 bugproxy ubuntu: assignee Skipper Bug Screeners (skipper-screen-team)
2019-03-06 15:19:30 bugproxy affects ubuntu linux (Ubuntu)
2019-03-06 15:22:19 Frank Heimes bug task added ubuntu-z-systems
2019-03-06 15:22:25 Frank Heimes ubuntu-z-systems: status New Triaged
2019-03-06 15:22:30 Frank Heimes ubuntu-z-systems: importance Undecided High
2019-03-06 15:22:43 Frank Heimes ubuntu-z-systems: assignee Canonical Kernel Team (canonical-kernel-team)
2019-03-12 09:12:33 Frank Heimes bug added subscriber Terry Rudd
2019-03-25 15:43:46 Frank Heimes description ---Problem Description--- The vfio-ap driver will create a matrix device in sysfs without a subsystem link. This triggers failures in libudev that might also lead to libvirt errors (e.g. see https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html) The proper fix is to add a subsystem link (e.g. by providing a dummy bus). A fix for that is upstream in master branch already for kernel 5.1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99 This need to be applied to Bionic, Cosmic and Disco SRU Justification: [Impact] * The vfio-ap driver will create a matrix device in sysfs without a subsystem link. * This causes failures in libudev that might also lead to libvirt errors. * A fix is upstream in master branch for kernel 5.1 [Fix] * 36360658eb5a6cf04bb9f2704d1e4ce54037ec99 3636065 "s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem" [Test Case] * An s390x machine with at least one CryptoExpress card, where at least one AP and one 'Domain' is assigned to a particular LPAR. * Now running virsh nodedev-list before (and later after) construction the matrix device should expose the issue. * For details about how to setup a vfio-ap matrix device see: http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html (see 2nd bullet: virtio-ap) [Regression Potential] * The regression potential can be considered as low since it only affects the s390x platform * and there it only affects the usage of AP (CryptoExpress) cards and it's driver/module * and again only affects the recently introduced virtual IO function of AP (vfio-ap). [Other Info] * It was already briefly discussed here: https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html as well as reviewed and pushed. * Commit 3636065 from v5.1-rc1 * This affects ccw cards and their vf only, NOT vf of PCI/PCIe cards! * For details on virtio-ap/vfio-ap see bullet #2 here: http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html _________________________ ---Problem Description--- The vfio-ap driver will create a matrix device in sysfs without a subsystem link. This triggers failures in libudev that might also lead to libvirt errors (e.g. see https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html) The proper fix is to add a subsystem link (e.g. by providing a dummy bus). A fix for that is upstream in master branch already for kernel 5.1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99 This need to be applied to Bionic, Cosmic and Disco
2019-03-27 13:13:54 Seth Forshee nominated for series Ubuntu Cosmic
2019-03-27 13:13:54 Seth Forshee bug task added linux (Ubuntu Cosmic)
2019-03-27 13:13:54 Seth Forshee nominated for series Ubuntu Disco
2019-03-27 13:13:54 Seth Forshee bug task added linux (Ubuntu Disco)
2019-03-27 13:13:54 Seth Forshee nominated for series Ubuntu Bionic
2019-03-27 13:13:54 Seth Forshee bug task added linux (Ubuntu Bionic)
2019-03-27 13:14:32 Seth Forshee linux (Ubuntu Disco): status New Fix Committed
2019-03-27 13:21:59 Frank Heimes ubuntu-z-systems: status Triaged In Progress
2019-03-29 06:08:46 Khaled El Mously linux (Ubuntu Bionic): status New Fix Committed
2019-03-29 06:08:49 Khaled El Mously linux (Ubuntu Cosmic): status New Fix Committed
2019-03-29 06:39:04 Frank Heimes ubuntu-z-systems: status In Progress Fix Committed
2019-04-04 18:01:52 Ubuntu Kernel Bot tags architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804 architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804 verification-needed-cosmic
2019-04-04 18:04:33 Ubuntu Kernel Bot tags architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804 verification-needed-cosmic architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804 verification-needed-bionic verification-needed-cosmic
2019-04-05 12:49:24 Frank Heimes tags architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804 verification-needed-bionic verification-needed-cosmic architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804 verification-done-bionic verification-needed-cosmic
2019-04-05 13:07:30 Frank Heimes tags architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804 verification-done-bionic verification-needed-cosmic architecture-s39064 bugnameltc-175967 severity-high targetmilestone-inin1804 verification-done verification-done-bionic verification-done-cosmic
2019-04-23 21:35:02 Launchpad Janitor linux (Ubuntu Cosmic): status Fix Committed Fix Released
2019-04-23 21:35:02 Launchpad Janitor cve linked 2017-5715
2019-04-24 06:47:01 Frank Heimes linux (Ubuntu Disco): status Fix Committed Fix Released
2019-04-24 07:39:21 Launchpad Janitor linux (Ubuntu Bionic): status Fix Committed Fix Released
2019-04-24 07:39:21 Launchpad Janitor cve linked 2017-5754
2019-04-24 07:39:21 Launchpad Janitor cve linked 2018-3639
2019-04-24 08:31:37 Frank Heimes linux (Ubuntu): status Fix Committed Fix Released
2019-04-24 08:31:42 Frank Heimes ubuntu-z-systems: status Fix Committed Fix Released