Page MenuHomeFreeBSD

[rtsock] Enforce netmask/RTF_HOST consistency
ClosedPublic

Authored by melifaro on Apr 23 2021, 9:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jan 14 2024, 1:38 AM
Unknown Object (File)
Dec 23 2023, 12:38 AM
Unknown Object (File)
Dec 18 2023, 3:33 PM
Unknown Object (File)
Dec 11 2023, 7:25 AM
Unknown Object (File)
Nov 8 2023, 8:35 PM
Unknown Object (File)
Sep 7 2023, 5:48 AM
Unknown Object (File)
Sep 6 2023, 8:50 AM
Unknown Object (File)
Sep 3 2023, 9:31 AM
Subscribers

Details

Summary

Traditionally we had 2 sources of information whether the added/delete route request targets network or a host route:
netmask (RTA_NETMASK) and RTF_HOST flag.

The former one is tricky: netmask can be empty or can explicitly specify the host netmask. Parsing netmask sockaddr requires per-family parsing and that's what rtsock code traditionally avoided. As a result, consistency was not enforced and it was possible to specify network with the RTF_HOST flag and vice versa.

Continue normalization efforts from D29826 and D29826 and ensure that RTF_HOST flag always reflects host/network data from netmask field.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable