diff options
| author | Petr Machata <petrm@nvidia.com> | 2024-12-09 12:05:31 +0100 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2024-12-10 18:26:24 -0800 |
| commit | bbe4b41259a3e255a16d795486d331c1670b4e75 (patch) | |
| tree | dd9f59ae1baacb732a332fde024312616025d16d /net/unix/af_unix.c | |
| parent | 24c6843b7393ebc80962b59d7ae71af91bf0dcc1 (diff) | |
| download | linux-bbe4b41259a3e255a16d795486d331c1670b4e75.tar.gz linux-bbe4b41259a3e255a16d795486d331c1670b4e75.tar.bz2 linux-bbe4b41259a3e255a16d795486d331c1670b4e75.zip | |
Documentation: networking: Add a caveat to nexthop_compat_mode sysctl
net.ipv4.nexthop_compat_mode was added when nexthop objects were added to
provide the view of nexthop objects through the usual lens of the route
UAPI. As nexthop objects evolved, the information provided through this
lens became incomplete. For example, details of resilient nexthop groups
are obviously omitted.
Now that 16-bit nexthop group weights are a thing, the 8-bit UAPI cannot
convey the >8-bit weight accurately. Instead of inventing workarounds for
an obsolete interface, just document the expectations of inaccuracy.
Fixes: b72a6a7ab957 ("net: nexthop: Increase weight to u16")
Signed-off-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
Reviewed-by: David Ahern <dsahern@kernel.org>
Link: https://patch.msgid.link/b575e32399ccacd09079b2a218255164535123bd.1733740749.git.petrm@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions