Le 29/08/2025 à 18:20, disparage.solvency678@??? a écrit :
> On Fri, Aug 29, 2025 at 10:31:17AM +0200, Didier Kryn wrote:
>
>>>> You don't need to reboot after kernel upgrade. The new kernel is
>>>> loaded on next reboot, but the previous one remains perfectly
>>>> functionnal; it just lacks the latest refinement or security fix
>>>> which you are most often not concerned with.
>>> What about modules? Presumably if you're upgrading the kernel
>>> image you're also upgrading the modules tree. If that
>>> actually*overwrites* the modules tree being used by the running
>>> kernel, i.e. if the upstream kernel version didn't change, I see
>>> potential grief when the running kernel tries to load a module
>>> from the new tree.
>> The modules are not overwritten. They are stored under /lib/modules,
>> in which you can find one directory tree per kernel version. And
>> modutils loads the modules corresponding to the running kernel
>> version.
> Yes. But the *package* can be, and on my "desktop" is, upgraded with
> the same upstream kernel version (presumably patched in new /
> different ways).
>
> Here's how my distribution names the modules tree:
>
> /lib/modules/6.12.10-76061203-generic
>
> this gets updated over and over, at least monthly. With the same name.
>
    Well, this tells you that the directory has been modified, not that
any module has been. Even if a module has been modified to fix a bug,
this doesn't change the kernel/module API, meaning it remains all
compatible.

    Since it doesn't correspond to a new kernel version, it means that
the Debian kernel package maintainer has applied or modified a patch to
the given module. It doubt they would do that for any other reason than
a bug fix.

--     Didier