This bug was fixed in the package linux-azure - 5.4.0-1039.41
---------------
linux-azure (5.4.0-1039.41) focal; urgency=medium
* focal/linux-azure: 5.4.0-1039.41 -proposed tracker (LP: #1912002)
* Use Azure host for time keeping in all images (LP: #1896784)
- hv_utils: return error if host timesysnc update is stale
- hv_utils: drain the timesync packets on onchannelcallback
* [linux-azure] Batch hibernate and resume IO requests (LP: #1904458)
- PM: hibernate: Batch hibernate and resume IO requests
linux-azure (5.4.0-1038.40) focal; urgency=medium
* focal/linux-azure: 5.4.0-1038.40 -proposed tracker (LP: #1911317)
[ Ubuntu: 5.4.0-63.71 ]
* focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333)
* overlay: permission regression in 5.4.0-51.56 due to patches related to
CVE-2020-16120 (LP: #1900141)
- ovl: do not fail because of O_NOATIME
* Focal update: v5.4.79 upstream stable release (LP: #1907151)
- net/mlx5: Use async EQ setup cleanup helpers for multiple EQs
- net/mlx5: poll cmd EQ in case of command timeout
- net/mlx5: Fix a race when moving command interface to events mode
- net/mlx5: Add retry mechanism to the command entry index allocation
* Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770)
- mt76: fix fix ampdu locking
* [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports
topology where zoning is enabled in expander (LP: #1899802)
- scsi: mpt3sas: Define hba_port structure
- scsi: mpt3sas: Allocate memory for hba_port objects
- scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device()
- scsi: mpt3sas: Update hba_port's sas_address & phy_mask
- scsi: mpt3sas: Get device objects using sas_address & portID
- scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port()
- scsi: mpt3sas: Get sas_device objects using device's rphy
- scsi: mpt3sas: Update hba_port objects after host reset
- scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough
- scsi: mpt3sas: Handling HBA vSES device
- scsi: mpt3sas: Add bypass_dirty_port_flag parameter
- scsi: mpt3sas: Handle vSES vphy object during HBA reset
- scsi: mpt3sas: Add module parameter multipath_on_hba
- scsi: mpt3sas: Bump driver version to 35.101.00.00
[ Ubuntu: 5.4.0-62.70 ]
* focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144)
* CVE-2020-28374
- SAUCE: target: fix XCOPY NAA identifier lookup
* Packaging resync (LP: #1786013)
- update dkms package versions
-- Marcelo Henrique Cerri <marcelo.ce...@canonical.com> Mon, 18 Jan
2021 09:44:59 -0300
** Changed in: linux-azure (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28374
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1896784
Title:
Use Azure host for time keeping in all images
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Focal:
Fix Released
Status in linux-azure-4.15 source package in Focal:
Invalid
Bug description:
SRU Justification:
[Impact]
Microsoft would like to request a change to the time keeping method in
the Azure images.
We would like to request that an Azure image uses the Azure host for
time sync by default. This will require the use of the Chrony
package.
The Chrony package would need to be installed by default in all images
and be configured to use /dev/ptp0 for timekeeping.
There is a request for two patches to be backported so Chrony time can
stay in sync before being set as the default.
Patches are already in the 5.8 kernel. Only needed for azure 5.4 and
4.15
[Fix]
backport these two patches:
b46b4a8a57c3 ("hv_utils: drain the timesync packets on onchannelcallback")
90b125f4cd26 ("hv_utils: return error if host timesysnc update is stale")
[Test Case]
Desired test cases:
- verify Chrony time can stay in sync
- verify caller is notified if host timesync update is stale
- verify all timesync packets are drained on onchannelcallback to avoid
stale packets
Microsoft holds test cases for the above. They verified a 4.15 and 5.4
test kernels with the above patches backported to work as expected.
[Regression Potential]
Caller may get an error now if host timesync messages were not
processed by the guest. This wasn't getting reported to the caller
before and may appear to be a regression if it occurs.
Regression potential may also lay in still incorrectly managing
timesync packets on onchannelcallback.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1896784/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
