[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

[Thadeu Lima de Souza Cascardo]

The build failed on jammy because of a new shellcheck warning, which was
fixed in Debian already. See https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1002270.

I have uploaded a merge to a PPA, where it built just fine. I am
attaching the debdiff for that.

Cascardo.

** Bug watch added: Debian Bug tracker #1002270
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002270

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
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 Committed
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