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 ** Changed in: linux-azure (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1904458 Title: [linux-azure] Batch hibernate and resume IO requests Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: Fix Released Status in linux-azure source package in Groovy: Fix Released Bug description: [Impact] Microsoft would like to request the following upstream commit in all releases supported on Azure. This commit improves a signification delay in hibernation/resume: 55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests") Details of this commit: Hibernate and resume process submits individual IO requests for each page of the data, so use blk_plug to improve the batching of these requests. Testing this change with hibernate and resumes consistently shows merging of the IO requests and more than an order of magnitude improvement in hibernate and resume speed is observed. One hibernate and resume cycle for 16GB RAM out of 32GB in use takes around 21 minutes before the change, and 1 minutes after the change on a system with limited storage IOPS. [Test Case] Follow the steps described here: https://bugs.launchpad.net/ubuntu/+source/linux- azure/+bug/1880032/comments/14 And compare the time need to save the instance state. [Where problems could occur] Considering the size of the patch and the code it touches, the most likely issues are related to hibernation itself. Considering the hibernation isn't officially support, any hibernation issues should even considered regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+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