Re: Stale modules (Re: panic in the morning)

[ Available lists | Index of freebsd-current | Month of Apr 2000 | Week of 20 Apr 2000 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Paul Richards <paul@originative.co.uk>
Date
20 Apr 2000 03:56:13
Subject
Re: Stale modules (Re: panic in the morning)
Message-ID
38FEE248.62AF3FE6@originative.co.uk

Referenced by

[ Hide this part ]
Warner Losh wrote:
>
> In message <000365a645d89ae9_mailit@mail.pacbell.net> Alex Zepeda writes:
> : Perhaps it's time to implement some sort of versioning in the modules to
> : prevent them from being loaded into the incorrect kernel.
>
> In theory that sounds nice, but in -current the kernel ABI changes too
> quickly for that to be effecitve. The general rule in -current is
> that the modules must be compiled at the same time as the kernel, or
> from the same sources. Anything else might work, but is unsupported.
> I don't know of a good way to serialize (eg assign a serial number to)
> the sources that would work.

Why not just use a UTC timestamp? If your kernel is newer than the
module then don't load the module. Maybe make it a sysctl as well so
that rapid developer folks can disable it.

Even if it was used just as a warning it would remind people to think
about the modules. I've lost count of the number of times that I've
chased a kernel bug before remembering to rebuild modules.

I know a timestamp doesn't guarantess ABI compatibility but it solves
the most common problem, which is rebuilding a kernel but forgetting to
rebuild the modules.

Paul.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Elapsed time: 0.148 seconds