This bug was fixed in the package linux-aws - 5.4.0-1037.39
---------------
linux-aws (5.4.0-1037.39) focal; urgency=medium
* focal/linux-aws: 5.4.0-1037.39 -proposed tracker (LP: #1911314)
* aws: network performance regression due to initial TCP receive buffer size
change (LP: #1910200)
- tcp: select sane initial rcvq_space.space for big MSS
* Disable Atari partition support for linux-aws (LP: #1908264)
- [Config] Disable Atari partition support
* aws: xen-netfront: prevent potential error on hibernate (LP: #1906850)
- SAUCE: xen-netfront: prevent unnecessary close on hibernate
[ 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
-- Kelsey Skunberg <kelsey.skunb...@canonical.com> Wed, 13 Jan 2021
19:01:10 -0700
--
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/1908264
Title:
Disable Atari partition support for cloud kernels
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-azure-4.15 package in Ubuntu:
Invalid
Status in linux-aws source package in Xenial:
Fix Committed
Status in linux-azure source package in Xenial:
Invalid
Status in linux-azure-4.15 source package in Xenial:
Invalid
Status in linux-aws source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-aws source package in Focal:
Fix Released
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-aws source package in Groovy:
Fix Committed
Status in linux-azure source package in Groovy:
Fix Committed
Status in linux-azure-4.15 source package in Groovy:
Invalid
Status in linux-aws source package in Hirsute:
In Progress
Status in linux-azure source package in Hirsute:
Invalid
Status in linux-azure-4.15 source package in Hirsute:
Invalid
Bug description:
[Impact]
Atari partition tables have very broad specifications, and can spontaneously
show up on uncleared disks with "garbage" data. There have been reports of
misinterpreted AHDI partition tables before (see [0] and [1]), usually as an
unintended side-effect of using non-zeroed disks. Users of this specific
partition scheme are unlikely to be on AWS instances, so we should disable them.
[0]
https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/
[1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html
[Test Case]
Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r)
[Fix]
Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu
[Regression Potential]
There could be unexpected dependencies on Atari partitions that are impacted
by this change. Considering Atari hardware hasn't been produced in a long time,
and is unlikely to be used in AWS instances, the regression potential should be
very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+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
