Page MenuHomeFreeBSD

netlink: store osreldate of the process in the netlink pcb
Needs ReviewPublic

Authored by glebius on Apr 30 2026, 5:45 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jun 5, 7:33 AM
Unknown Object (File)
Thu, Jun 4, 7:37 AM
Unknown Object (File)
Wed, Jun 3, 10:31 PM
Unknown Object (File)
May 17 2026, 9:09 AM
Unknown Object (File)
May 17 2026, 7:02 AM
Unknown Object (File)
May 14 2026, 9:21 AM
Unknown Object (File)
May 12 2026, 8:46 PM
Unknown Object (File)
May 12 2026, 12:02 PM

Details

Reviewers
pouria
melifaro
Group Reviewers
network
Summary

This will allow to provide backwards compatibility shims.

Diff Detail

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

Event Timeline

Do you have an example of the kind of backwards compat we'd provide?

Do you have an example of the kind of backwards compat we'd provide?

Hi,
This change was initially proposed to support my routing-stack changes (metric for example).
One of the cases is D57266.
My original approach used a 32-bit weight in the nexthop struct, but I rewrote the metric implementation and kept the 8-bit weight as-is in netlink.
The reason was BIRD, I saw @melifaro's commits on it and learned he wanted FreeBSD's netlink to remain as close to Linux's version as possible.

Please keep this review open if possible. the use case will come up soon, though I don't know exactly when or for what.

The reason was BIRD, I saw @melifaro's commits on it and learned he wanted FreeBSD's netlink to remain as close to Linux's version as possible.
Please keep this review open if possible. the use case will come up soon, though I don't know exactly when or for what.

+1. Yes this sounds like the best approach to me. The netlink userland wrapper situation on Linux itself isn't ideal and I might even put in the cycles to port SNL to it if it comes to that. I might have other plans...