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

marking built/installed modules as rebuild-needed #406

Open
anbe42 opened this issue Mar 16, 2024 · 0 comments
Open

marking built/installed modules as rebuild-needed #406

anbe42 opened this issue Mar 16, 2024 · 0 comments

Comments

@anbe42
Copy link
Contributor

anbe42 commented Mar 16, 2024

When upgrading a linux-header (or linux-image) package without a kernel version change, we should rebuild all modules for that kernel. I'm a bit reluctant to unbuild all modules during preinst, I'd rather "mark" them for rebuilding during the next autoinstall run. Maybe this could be achieved by creating a flag file in the previously built module directory.
All actions that require the module to be built (build, install, autoinstall) should automatically unbuild the module if that flag file exists (which would cause the flag file to be deleted) before carrying out their operation.
I'm not sure whether we should change the status output if a module is in that state.
Ideally this should be implemented directly in dkms to be called from the scripts, e.g.
dkms mark-for-rebuild -k <kernel> [-m/-v module/version]
This should also operate on AUTOINSTALL=no modules.

Which also raises another question: shouldn't kernel_prerm.d_dkms.in act on 'built' modules, too, in addition to 'installed' ones?

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

No branches or pull requests

1 participant