Speaking as someone who's not very familiar with the Debian kernel
development processes I am in favor of reverting the commit until we know
for sure that the AWS Xen fleet upgrade is complete and pushing a new
release, especially if it's possible to only apply the revert to the -cloud
kernels.

Currently users of those older instance types in AWS have no other option
than to stay on an old insecure kernel or switch to a different instance
type (which may be impossible if they have reserved instances they need to
utilize).

With the recent CVE-2022-0847 (Dirty Pipe) vulnerability they may end up in
a situation where they reboot their machines to complete patching and then
have them be rendered unusable.

Reply via email to