sts-sponsors team mailing list archive

[Mauricio Faria de Oliveira <1942784@xxxxxxxxxxxxxxxxxx>]

Hey Jo,

Thanks for the debdiff!

...

So, it looks like the 2 commits for dmesg/printk are actually LP#1921403
that you handled previously?

For better tracking/documentation purposes, the right thing to do would be to keep these 2 patches
associated with that bug (well, it requires an SRU template now, but you already have it on here.)

Thus I added a Focal task there, and it can be properly referenced in
the changelog.

...

And the first commit, for uts_namespace.name should go into Hirsute too, right? I see it's not in
the source package. Since we're adding it back to Focal, it should get into the later releases too.

Adding a Hirsute task here.  Could you please provide a debdiff for
Hirsute as well?

...

BTW, the debdiff has a `makedumpdife` typo on changelog (that was funny.
:)

And despite the patches being DEP3 tagged as 'upstream', at least one of them
needs changes to apply (uts_namespace.name, hunk 5), so it should be tagged
'backport' (or just leave the first, optional field out.)

...

And last but not least, since the patches are architecture independent, 
would you mind testing on the supported architectures? I know it seems
overkill per the changes on these patches, but we're better safe than
sorry, particularly on the kernel crash dump path.

If some arch isn't available on canonistack, please see some old notes [1]
that I used to get them running in QEMU to verify installer changes
(s390x emulation was surprisingly fast, and arm64 worked well enough;
I guess it should be ok to skip armhf, and of course, no more i386 on F/H.)

Uh, on both kernels :/ But that should be the least of the suggested
work steps, once the VM is already installed w/ the GA kernel. :)

...

Thanks again!
Mauricio

[1] https://pastebin.ubuntu.com/p/YXBF9dFFp3/

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  In Progress
Status in makedumpfile source package in Hirsute:
  In Progress

Bug description:
  [IMPACT]

  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into exhausting all storage on the host.
  This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 'uts_namespace.name' offset in VMCOREINFO).

  In addition the dmesg.<timestamp> is not created.
  This can be resolved with the following two commits  :
  - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  On the console we can see that makedumpfile fails and `falls back to cp`. 
  In /var/crash we can see that no dmesg file is created and instead of the dump file
  the uncompressed vmcoreinfo is created.

  [WHERE PROBLEMS COULD OCCUR]

  The 3 commits pulled into focal make makedumpfile compatible with the 5.11 kernel.
  Any regression potential would involve the crash dump not being created after a crash in case kdump is configured.

  [OTHER]

  Only Focal with 5.11 kernel is affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions