RFC l3mdev icmp error route lookup fixes
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 RFC Latest3 patches 11 repliesIn review
- v13 patches 6 repliesSuperseded
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | ipv4/icmp: l3mdev: Perform icmp error route lookup on source device routing table (v2)net/ | +21 | 0 replies | |
| 2/3 | ipv6/icmp: l3mdev: Perform icmp error route lookup on source device routing table (v2)net/ net/ | +5 | 0 replies | |
| 3/3 | selftests: Add VRF icmp error route lookup testtools/ tools/ | +476 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [RFC PATCH v2 0/3] l3mdev icmp error route lookup fixes
Hi,
Here is an updated series of fixes for ipv4 and ipv6 which which ensure the route lookup is performed on the right routing table in VRF configurations when sending TTL expired icmp errors (useful for traceroute).
It includes tests for both ipv4 and ipv6.
These fixes address specifically address the code paths involved in sending TTL expired icmp errors. As detailed in the individual commit messages, those fixes do not address similar issues related to network namespaces and unreachable / fragmentation needed messages, which appear to use different code paths.
Thanks,
Mathieu
Mathieu Desnoyers (2):
ipv4/icmp: l3mdev: Perform icmp error route lookup on source device
routing table (v2)
ipv6/icmp: l3mdev: Perform icmp error route lookup on source device
routing table (v2)
Michael Jeanson (1):
selftests: Add VRF icmp error route lookup test
net/ipv4/icmp.c | 23 +- net/ipv6/icmp.c | 7 +- net/ipv6/ip6_output.c | 2 - tools/testing/selftests/net/Makefile | 1 + .../selftests/net/vrf_icmp_error_route.sh | 475 ++++++++++++++++++ 5 files changed, 502 insertions(+), 6 deletions(-) create mode 100755 tools/testing/selftests/net/vrf_icmp_error_route.sh
Signature · 1 line
2.17.1