Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't Add Empty fadump="" Kernel Parameter [SLE-15-SP7] #142

Merged
merged 4 commits into from
Sep 18, 2024

Conversation

shundhammer
Copy link
Contributor

@shundhammer shundhammer commented Sep 17, 2024

Target Branch

This merges #141 to SLE-15-SP7.

Bugzilla

https://bugzilla.suse.com/show_bug.cgi?id=1230359

Problem

On the PPC64 architecture, when fadump (Firmware Assisted Dump) kernel dumps are supported, but the user chooses not to enable that in the YaST UI, the fadump kernel parameter is still added, albeit with an empty argument:

fadump=""

This does not really do any harm, but user scripts that check for this kernel parameter may be confused.

Fix

Don't add this parameter if its argument is empty. If it's already there, but empty, remove it with the special :missing argument.

Test

  • Hacked up a (x86_64) TW VM: Moved away the original kdumptool and replaced it with a shell script that writes the values from https://bugzilla.suse.com/show_bug.cgi?id=1230359#c12 to stdout to mock fadump support.

  • Manual test with yast2 bootloader and yast2 kdump.

  • Checked the original kernel parameters in /etc/default/grub and in /boot/grub2/grub.cfg

  • Double-checked the kernel parameters with yast2 bootloader

  • Started yast2 kdump:

    • Enabled kdump
    • Enabled fadump
    • Saved the configuration
  • Checked the kernel parameters again in /etc/default/grub and in /boot/grub2/grub.cfg: There should now be an fadump="on" parameter.

  • Started yast2 kdump again:

    • Enabled kdump
    • Disabled fadump
    • Saved the configuration
    • Checked the kernel parameters again in /etc/default/grub and in /boot/grub2/grub.cfg: There should now not an fadump=" parameter.
  • Edited /etc/default/grub and added an empty fadump= parameter

  • Started yast2 kdump again:

    • Enabled kdump
    • Disabled fadump
    • Saved the configuration
    • Checked the kernel parameters again in /etc/default/grub and in /boot/grub2/grub.cfg: There should now not an fadump=" parameter despite the manually added one.

Related PRs

@coveralls
Copy link

Coverage Status

coverage: 40.121% (-0.02%) from 40.144%
when pulling f8a2cd7 on huha-fadump-sp7
into 4550e67 on SLE-15-SP7.

@shundhammer shundhammer merged commit 775fbee into SLE-15-SP7 Sep 18, 2024
10 of 12 checks passed
@shundhammer shundhammer deleted the huha-fadump-sp7 branch September 18, 2024 08:38
@yast-bot
Copy link
Contributor

✔️ Internal Jenkins job #3 successfully finished
✔️ Created IBS submit request #345434

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants