| 2020-06-12 13:58:17 |
Joseph Salisbury |
bug |
|
|
added bug |
| 2020-06-12 14:16:52 |
Guilherme G. Piccoli |
bug |
|
|
added subscriber Guilherme G. Piccoli |
| 2020-06-13 09:03:19 |
Balint Harmath |
linux-azure (Ubuntu): status |
New |
Confirmed |
|
| 2020-10-07 16:53:03 |
Kelsey Steele |
description |
Microsoft would like to request two kdump related fixes in all releases supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible symptom is that the network is not functional in the kdump kernel, so the dump file must be stored on the local disk and cannot be written over the network.
The problem only occurs when Accelerated Networking is enabled. It’s a relatively obscure scenario, which is why the problem has not surfaced before now. But we have an important customer who wants the “dump-file-over-the-network” functionality to work. |
[Impact]
Microsoft would like to request two kdump related fixes in all releases supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible symptom is that the network is not functional in the kdump kernel, so the dump file must be stored on the local disk and cannot be written over the network.
The problem only occurs when Accelerated Networking is enabled. It’s a relatively obscure scenario, which is why the problem has not surfaced before now. But we have an important customer who wants the “dump-file-over-the-network” functionality to work.
[Test Case]
- Apply requested patches and boot into updated kernel
- Verify Accelerated Networking is enabled
- Set up kdump
- configure kdump to use SSH
- Test the crash dump mechanism and verify the kernel crash dump appears on the selected remote server
Further details for setting up kdump through testing can be found here:
https://ubuntu.com/server/docs/kernel-crash-dump
[Regression Potential]
Build & boot tested. Verified kdump works as intended over SSH after patches are applied.
Both 5.4 and 4.15 test kernels were sent to Microsoft. Both kernels signed off on and verified to resolve problem. |
|
| 2020-10-07 16:53:28 |
Kelsey Steele |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-10-07 16:53:28 |
Kelsey Steele |
bug task added |
|
linux-azure (Ubuntu Bionic) |
|
| 2020-10-07 16:53:28 |
Kelsey Steele |
nominated for series |
|
Ubuntu Focal |
|
| 2020-10-07 16:53:28 |
Kelsey Steele |
bug task added |
|
linux-azure (Ubuntu Focal) |
|
| 2020-10-07 21:16:04 |
Kelsey Steele |
description |
[Impact]
Microsoft would like to request two kdump related fixes in all releases supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible symptom is that the network is not functional in the kdump kernel, so the dump file must be stored on the local disk and cannot be written over the network.
The problem only occurs when Accelerated Networking is enabled. It’s a relatively obscure scenario, which is why the problem has not surfaced before now. But we have an important customer who wants the “dump-file-over-the-network” functionality to work.
[Test Case]
- Apply requested patches and boot into updated kernel
- Verify Accelerated Networking is enabled
- Set up kdump
- configure kdump to use SSH
- Test the crash dump mechanism and verify the kernel crash dump appears on the selected remote server
Further details for setting up kdump through testing can be found here:
https://ubuntu.com/server/docs/kernel-crash-dump
[Regression Potential]
Build & boot tested. Verified kdump works as intended over SSH after patches are applied.
Both 5.4 and 4.15 test kernels were sent to Microsoft. Both kernels signed off on and verified to resolve problem. |
[Impact]
Microsoft would like to request two kdump related fixes in all releases supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible symptom is that the network is not functional in the kdump kernel, so the dump file must be stored on the local disk and cannot be written over the network.
The problem only occurs when Accelerated Networking is enabled. It’s a relatively obscure scenario, which is why the problem has not surfaced before now. But we have an important customer who wants the “dump-file-over-the-network” functionality to work.
[Test Case]
- Apply requested patches and boot into updated kernel
- Verify Accelerated Networking is enabled
- Set up kdump
- configure kdump to use SSH
- Test the crash dump mechanism and verify the kernel crash dump appears on the selected remote server
Further details for setting up kdump through testing can be found here:
https://ubuntu.com/server/docs/kernel-crash-dump
[Regression Potential]
Patches are only targeted to azure kernels.
Patches are desgiend to release allocated resources remaining after
error cases in hv_pci_probe() or PCI devices not being shut down
properly. if those resources are still not correctly released, then
entering D0 state in kdump kernel could continue to fail.
Potential for finding regression with freeing resources or still failing to enter D0 state in the kdump kernel even after all resources have been
released.
Build & boot tested. Verified kdump works as intended over SSH after patches are applied.
Both 5.4 and 4.15 test kernels were sent to Microsoft. Both kernels signed off on and verified to resolve problem. |
|
| 2020-10-09 20:41:43 |
Ian May |
linux-azure (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2020-10-09 21:15:12 |
Ian May |
linux-azure (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2020-11-30 15:46:41 |
Launchpad Janitor |
linux-azure (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-11-30 15:46:41 |
Launchpad Janitor |
cve linked |
|
2020-12351 |
|
| 2020-11-30 15:46:41 |
Launchpad Janitor |
cve linked |
|
2020-12352 |
|
| 2020-11-30 15:46:41 |
Launchpad Janitor |
cve linked |
|
2020-14351 |
|
| 2020-11-30 15:46:41 |
Launchpad Janitor |
cve linked |
|
2020-24490 |
|
| 2020-11-30 15:46:41 |
Launchpad Janitor |
cve linked |
|
2020-8694 |
|
| 2020-12-02 06:01:58 |
Launchpad Janitor |
linux-azure (Ubuntu): status |
Confirmed |
Fix Released |
|
