diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-10-07 19:47:15 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-07 19:47:15 -0700 |
| commit | 2b358bb4af0e06f154d27115f17150a8c2486e4f (patch) | |
| tree | 755e29b7e2ad9ce7ce0b76d62a2fb2c2965208b3 /include/linux | |
| parent | 8df0638138d3e0344fd1fb36cf2d1ca1cf5028f0 (diff) | |
| parent | d476bb7c0efd56aa3d579114802305e4500bec85 (diff) | |
Merge branch 'vxlan-generalize-and-refine-drop-reasons'
Anton Danilov says:
====================
vxlan: generalize and refine drop reasons
This series makes two vxlan drop reasons generic, so that other tunnels
can report the same conditions with them, and makes the reasons vxlan
reports for two other failures more precise.
Patch 1 renames VXLAN_INVALID_HDR and VXLAN_VNI_NOT_FOUND to
TUNNEL_INVALID_HDR and TUNNEL_NOT_FOUND. Their values stay the same;
the names vxlan drops are reported with change.
Patch 2 makes __iptunnel_pull_header() and iptunnel_pull_header() return
a drop reason. Until now they returned -ENOMEM for any failure, so a
packet too short to pull looked like an allocation failure. The three
callers in ip_gre and ip6_gre that tested the result with "< 0" test for
a non-zero value instead. Patch 3 has vxlan report the reason these
functions now return: PKT_TOO_SMALL instead of NOMEM for an inner frame
shorter than an Ethernet header.
Patch 4 has vxlan report a route that goes out of the vxlan device
itself as RECURSION_LIMIT instead of IP_OUTNOROUTES, and adds this case
to the description of RECURSION_LIMIT.
These were patches 1-3 and 14 of v5 of "tunnels: add core and gre drop
reasons", split out as Ido suggested. The conversion of ip_tunnel,
ip6_tunnel and GRE, the rest of that series, will follow once these
are in.
====================
Link: https://patch.msgid.link/20261005201417.906344-1-littlesmilingcloud@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
