linux-azure: 4.18.0-1005.5 -proposed tracker
Bug #1802752 reported by
Stefan Bader
This bug report is a duplicate of:
Bug #1805244: linux-azure: 4.18.0-1006.6 -proposed tracker.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kernel SRU Workflow |
Fix Released
|
Medium
|
Unassigned | ||
Automated-testing |
Confirmed
|
Medium
|
Canonical Kernel Team | ||
Certification-testing |
Invalid
|
Medium
|
Canonical Hardware Certification | ||
Prepare-package |
Fix Released
|
Medium
|
Khaled El Mously | ||
Prepare-package-meta |
Fix Released
|
Medium
|
Khaled El Mously | ||
Prepare-package-signed |
Fix Released
|
Medium
|
Khaled El Mously | ||
Promote-to-proposed |
Fix Released
|
Medium
|
Łukasz Zemczak | ||
Promote-to-security |
New
|
Medium
|
Ubuntu Stable Release Updates Team | ||
Promote-to-updates |
New
|
Medium
|
Ubuntu Stable Release Updates Team | ||
Regression-testing |
Confirmed
|
Medium
|
Canonical Kernel Team | ||
Security-signoff |
In Progress
|
Medium
|
Canonical Security Team | ||
Stakeholder-signoff |
Confirmed
|
Medium
|
linux-azure stakeholder signoff | ||
Upload-to-ppa |
New
|
Medium
|
Canonical Kernel Team | ||
Verification-testing |
Confirmed
|
Medium
|
Canonical Kernel Team | ||
linux-azure (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This bug is for tracking the <version to be filled> upload package. This bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see: https:/
-- swm properties --
boot-testing-
kernel-
phase: Uploaded
reason:
automated-
regression-
security-signoff: Waiting for signoff
stakeholder-
verification-
CVE References
tags: | added: kernel-release-tracking-bug |
tags: | added: kernel-release-tracking-bug-live |
tags: | added: cosmic |
Changed in linux-azure (Ubuntu Cosmic): | |
status: | New → Confirmed |
Changed in linux-azure (Ubuntu): | |
status: | New → Invalid |
Changed in linux-azure (Ubuntu Cosmic): | |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | New → In Progress |
importance: | Undecided → Medium |
tags: | added: kernel-sru-cycle-2018.11.12-1 |
tags: | added: kernel-sru-derivative-of-1802743 |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
summary: |
- linux-azure: <version to be filled> -proposed tracker + linux-azure: 4.18.0-1005.5 -proposed tracker |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: block-proposed-cosmic |
tags: | added: block-proposed |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in linux-azure (Ubuntu): | |
status: | Invalid → Fix Released |
tags: | removed: kernel-release-tracking-bug-live |
Changed in kernel-sru-workflow: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
This bug was fixed in the package linux-azure - 4.18.0-1006.6
---------------
linux-azure (4.18.0-1006.6) cosmic; urgency=medium
* linux-azure: 4.18.0-1006.6 -proposed tracker (LP: #1805244)
* Accelerated networking (SR-IOV VF) broken in 18.10 daily (LP: #1794477)
- [Packaging] Move pci-hyperv and autofs4 back to linux-modules
linux-azure (4.18.0-1005.5) cosmic; urgency=medium
* linux-azure: 4.18.0-1005.5 -proposed tracker (LP: #1802752)
* [Hyper-V] Fix IRQ spreading on NVMe devices with lower numbers of channels
(LP: #1802358)
- SAUCE: genirq/affinity: Spread IRQs to all available NUMA nodes
- SAUCE: irq/matrix: Split out the CPU selection code into a helper
- SAUCE: irq/matrix: Spread managed interrupts on allocation
- SAUCE: genirq/matrix: Improve target CPU selection for managed interrupts.
[ Ubuntu: 4.18.0-12.13 ]
* linux: 4.18.0-12.13 -proposed tracker (LP: #1802743) _available( ) returncodes VSIE_RESTART GET_INFO ioctl S390_AP_ IOMMU and set CONFIG_VFIO_AP to module. MNT_LOCKED mounts
* [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
- s390/zcrypt: Add ZAPQ inline function.
- s390/zcrypt: Review inline assembler constraints.
- s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.
- s390/zcrypt: fix ap_instructions
- KVM: s390: vsie: simulate VCPU SIE entry/exit
- KVM: s390: introduce and use KVM_REQ_
- KVM: s390: refactor crypto initialization
- s390: vfio-ap: base implementation of VFIO AP device driver
- s390: vfio-ap: register matrix device with VFIO mdev framework
- s390: vfio-ap: sysfs interfaces to configure adapters
- s390: vfio-ap: sysfs interfaces to configure domains
- s390: vfio-ap: sysfs interfaces to configure control domains
- s390: vfio-ap: sysfs interface to view matrix mdev matrix
- KVM: s390: interface to clear CRYCB masks
- s390: vfio-ap: implement mediated device open callback
- s390: vfio-ap: implement VFIO_DEVICE_
- s390: vfio-ap: zeroize the AP queues
- s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl
- KVM: s390: Clear Crypto Control Block when using vSIE
- KVM: s390: vsie: Do the CRYCB validation first
- KVM: s390: vsie: Make use of CRYCB FORMAT2 clear
- KVM: s390: vsie: Allow CRYCB FORMAT-2
- KVM: s390: vsie: allow CRYCB FORMAT-1
- KVM: s390: vsie: allow CRYCB FORMAT-0
- KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1
- KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2
- KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2
- KVM: s390: device attrs to enable/disable AP interpretation
- KVM: s390: CPU model support for AP virtualization
- s390: doc: detailed specifications for AP virtualization
- KVM: s390: fix locking for crypto setting error path
- KVM: s390: Tracing APCB changes
- s390: vfio-ap: setup APCB mask using KVM dedicated function
- [Config:] Enable CONFIG_
* Bypass of mount visibility through userns + mount propagation (LP: #1789161)
- mount: Retest MNT_LOCKED in do_umount
- mount: Don't allow copying MNT_UNBINDABLE|
* CVE-2018-18955: nested user namespaces with more than fiv...