Page MenuHomeFreeBSD

kmods: start embedding version information
Needs ReviewPublic

Authored by kevans on Aug 9 2025, 7:56 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Sep 28, 2:02 AM
Unknown Object (File)
Sat, Sep 20, 6:14 PM
Unknown Object (File)
Wed, Sep 17, 3:53 PM
Unknown Object (File)
Sep 17 2025, 1:09 PM
Unknown Object (File)
Sep 15 2025, 10:37 AM
Unknown Object (File)
Sep 13 2025, 12:21 PM
Unknown Object (File)
Sep 6 2025, 1:07 AM
Unknown Object (File)
Sep 2 2025, 7:55 AM
Subscribers
None

Details

Reviewers
imp
kib
jhb
emaste
Summary

If a freebsd-update patch touches a kmod that isn't in GENERIC, then the
kernel version according to freebsd-version will not be bumped. This
results in a little bit of a dilemma for users, as it's not clear that
the userland version being higher than the necessary patchlevel is
sufficient to be confident that the kmod is patched.

Start embedding version information into kmod builds like we do the
kernel, so that recommendations like what(1) can be used to resolve
these sorts of concerns. We might find a better solution in the future
and this will be somewhat OBE with pkgbase, but this seems like a
reasonable solution for stable/13 and stable/14 until EoL.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 66139
Build 63022: arc lint + arc unit

Event Timeline

kevans requested review of this revision.Aug 9 2025, 7:56 PM
kevans created this revision.
sys/conf/newvers.sh
341

Is that information useful for modules? I would understand osreldate and compiler_version embedding. But other stuff, like ostype, sccstag, and others, seems to be a historical garbage.