Fix route(8) incorrectly returning a zero exit code even when unable to find
the specified route with route -n get <route>.
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential D41882
route(8): fix `route not found` exit code and warn with netlink rcm on Sep 15 2023, 8:26 PM. Authored by Tags None Referenced Files
Subscribers
Details Fix route(8) incorrectly returning a zero exit code even when unable to find Sponsored by: Rubicon Communications, LLC ("Netgate")
Diff Detail
Event TimelineComment Actions I've not dug into it yet, but it looks like this causes the sys/netinet6 forward6:fwd_ip6_gu_icmp_gw_ll_fast_success and forward6:fwd_ip6_gu_icmp_gw_ll_slow_success tests to fail. Sample output: (kp@freebsd_current_zfs) /usr/tests/sys/netinet6 % sudo kyua debug forward6:fwd_ip6_gu_icmp_gw_ll_slow_success [11:05] Executing command [ jexec v6t-fff4--8373 route add -6 -host 2001:db8:6666:0000::fff4:4:8373 fe80::6c:e4ff:fe29:e20a%epair0b ] v6t-fff4--8373: removed Fail: stderr not empty --- /dev/null 2023-09-17 09:06:00.862100000 +0000 +++ /tmp/kyua.6ZklLH/2/work/check.jwEAdR/stderr 2023-09-17 09:06:00.859014000 +0000 @@ -0,0 +1 @@ +route: message indicates error: No error: 0 Files left in work directory after failure: created_interfaces.lst, created_jails.lst ifconfig: interface epair0a does not exist forward6:fwd_ip6_gu_icmp_gw_ll_slow_success -> failed: atf-check failed; see the output of the test for details I'm not sure if this is because there's something wrong with the patch or because there's something wrong with the test though. |