This bug was fixed in the package linux-aws - 5.4.0-1007.7
---------------
linux-aws (5.4.0-1007.7) focal; urgency=medium
[ Ubuntu: 5.4.0-21.25 ]
* CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling
-- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Fri, 27 Mar
2020 17:06:08 -0300
** Changed in: linux-aws (Ubuntu Focal)
Status: New => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1858618
Title:
linux-aws: swapoff optimization
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-aws-5.0 package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Fix Released
Status in linux-aws-5.0 source package in Bionic:
Fix Released
Status in linux-aws source package in Disco:
Fix Committed
Status in linux-aws-5.0 source package in Disco:
Invalid
Status in linux-aws source package in Eoan:
Fix Committed
Status in linux-aws-5.0 source package in Eoan:
New
Status in linux-aws source package in Focal:
Fix Released
Status in linux-aws-5.0 source package in Focal:
Invalid
Bug description:
[Impact]
When an instance in the AWS EC2 infrastructure is successfully
hibernated and resumed we want to deactivate the swap file as fast as
possible in order to make the instance available again for the user.
By default the kernel doesn't really optimize swapoff performance, it
tries to keep the whole system still usable and responsive while
swapoff is running.
However, in our specific use case, swapoff needs to complete as fast
as possible, so we may want to give swapoff I/O a higher priority and
use different heuristics in order to optimize the I/O and page
readahead generated by swapoff.
[Test Case]
Run the hibernation test on the AWS EC2 instances.
[Fix]
Apply a more aggressive swapin readahead policy that allows to improve
swapoff performance.
[Regression Potential]
Minimal, this change is only affecting the swapoff-related code and it
has been tested extensively with positive test results. The only
downside is that this different heuristic makes the system more
unresponsive during swapoff, but this is not a problem in the AWS
scenario, because (by explicit requirement) the user shouldn't be able
to use the instance during this swapoff phase.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1858618/+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
