This bug was fixed in the package kdump-tools - 1:1.6.10ubuntu1
---------------
kdump-tools (1:1.6.10ubuntu1) jammy; urgency=low
* Merge from Debian unstable. Remaining changes:
- debian/control/tests: sleep while waiting for systemd service.
- Bump amd64 crashkernel from 384M-:128M to 512M-:192M.
- Add a systemd-resolved service dependency in order kdump-tools is able
to resolve DNS when in kdump boot.
- Update default s390x crashkernel.
- Install the updated zipl.conf with ucf, so users will be able to
decide whether to pick any crashkernel changes.
kdump-tools (1:1.6.10) unstable; urgency=medium
* kdump-config: Fix FTBFS due to new shellcheck warning (Closes:
#1002270).
-- dann frazier <[email protected]> Thu, 24 Mar 2022 11:42:57 -0600
** Changed in: kdump-tools (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
Matching subscriptions: Maintainer
https://bugs.launchpad.net/bugs/1877533
Title:
[20.10 FEAT] Increase the crashkernel setting if the root volume is
luks2-encrypted
Status in Ubuntu on IBM z Systems:
In Progress
Status in kdump-tools package in Ubuntu:
Fix Released
Status in makedumpfile package in Ubuntu:
Invalid
Status in kdump-tools source package in Focal:
Invalid
Status in makedumpfile source package in Focal:
In Progress
Status in kdump-tools source package in Groovy:
Invalid
Status in makedumpfile source package in Groovy:
Won't Fix
Bug description:
Description:
In case the volume containing the root filesystem is encrypted using LUKS2
the memory used while unlocking the volume may exceed the size allocated to the
kdump kernel. This will lead to a failure while processing kdump and the dump
file will not be stored. Unfortunately, this condition may not be detected by a
client before a problem occurs.
The request is to have the kdump package installation script check for LUKS2
encryption (more precisely for Argon2i PBKDF, which is the root cause of the
high memory usage). If the condition is met, the installation procedure should
increase the crashkernel parameter to a higher value (>=512M)or issue a
warning, if the system memory is insufficient to reserve enough crashkernel
memory.
Business Case:
Pervasive Encryption and Secure Execution require encryption of the
filesystems in order to keep customer data secure at all times. With the
increasing usage of these technologies, the number of kdump will rise too,
typically at inconvenient times, when the kdump is triggered due to a real
customer issue.
With the suggested change, the number of customer complaints and effort to
handle them will be reduced.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
