CU206 test : Regarding the grub iommu=pt option

In the commit addressing the GRUB configuration:

https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=80e9d5130ba07968ad5b6754ece0177bd0ba9adb

core206: Remove iommu=pt from the kernel command line

Some users have added iommu=pt to /etc/default/grub to work around a crash in the Broadcom driver. This has been fixed in Linux 6.18.60 which is shipped in Core Update 205, so the workaround can be removed again.

The boot loader configuration is regenerated at the end of the update.

I understand the reason for removing this workaround, but I would like to raise a slightly different point.

To my knowledge, iommu=pt has never been part of the default configuration of any previous IPFire installation.
IPFire is open source, which allows users to make their own modifications and adapt the system to their specific needs. I believe this flexibility is one of its strengths.
If a user has deliberately added this option to /etc/default/grub, it is presumably for a specific reason. If it is no longer needed or causes problems, the user can decide to remove it.

I have not come across any bug report or community forum request suggesting that this option should be removed globally.
This is why I am not entirely sure why the update removes it for all users, including those who added it for reasons unrelated to the Broadcom driver.

In my own case, I use iommu=pt to avoid bandwidth limitations when routing traffic internally between the network interfaces (inter-NIC routing) of my IPFire server.
I previously discussed this here, in a fairly detailed exchange:
https://community.ipfire.org/t/ipfire-kernel-optimizations-for-10gb-wan-lan/15353/21?u=pscar13

This is a deliberate configuration choice on my part, and it has nothing to do with the Broadcom driver workaround.
Of course, I can simply add the option again after each GRUB configuration update, just as I do with other personal adjustments.

So, I am not reporting a problem or asking for a change. I simply wanted to understand the reasoning behind this particular change, since it seems to go beyond removing a workaround that is no longer needed.

The commit sounds like it removes a shipped workaround, not a ban on using iommu=pt. The key question is whether the core update rewrites /etc/default/grub; if it does, that is the real issue, because it wipes any deliberate local GRUB_CMDLINE_LINUX additions, not just the Broadcom workaround. Re-adding it is fine, but I would raise the overwrite behaviour separately so local customisations can survive updates.