[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.
[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
are unlikely to be used in AWS instances, the regression potential should be
very low.
[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.<email address hidden>/ /mail-index. netbsd. org/port- atari/1995/ 11/19/0001. html
[1] https:/
[Test Case] ATARI_PARTITION is not set in /boot/config- $(uname -r)
Ensure that CONFIG_
[Fix] ATARI_PARTITION in debian. aws/config/ config. common. ubuntu
Unset CONFIG_
[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
are unlikely to be used in AWS instances, the regression potential should be
very low.