Reputation: 31
Suppose I build a module in kernel 2.6.32-431, but I load it successfully in kernel 2.6.32-432. Can this module work properly? Or is it harm to system?
Upvotes: 0
Views: 638
Reputation: 61
As long as your changes complied successfully under the module build in your new kernel version, it should not be a problem. It should work normally 99%.
Upvotes: 0
Reputation: 6327
The version of your kernel is 2.6.32
.
The number you see after the dash (-432
) is an iteration of patchsets applied by your distribution's developers. Most of those changes likely are security patches.
Moreover, 2.6.32 kernel is an LTS release, which normally doesn't accept anything, but security updates and fixes for severe issues.
So, you should not worry that module compiled with 2.6.32-431
kernel sources won't work on 2.6.32-432
kernel.
What you should really worry about is that 2.6.32
kernel is not supported since February 2016
.
Upvotes: 3
Reputation: 66308
With such a little difference between kernel versions (2.6.32-431
vs 2.6.32-432
) and by passing checksum check (see e.g. this answer about checksum in Linux kernel modules), your module will very likely operate correctly.
Of course, no one can be sure about correctness.
Upvotes: 2