diff options
| author | David Ahern <dsa@cumulusnetworks.com> | 2016-01-04 09:09:27 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-01-04 22:58:30 -0500 |
| commit | b5bdacf3bb027ba0af4d61b38ec289bfc8b64372 (patch) | |
| tree | 1346f43639075874a2c82c5d67dad70a3b95e493 /include/Kbuild | |
| parent | 7ec2541aa7a026874930d6117e86fe2e76fb1587 (diff) | |
| download | linux-b5bdacf3bb027ba0af4d61b38ec289bfc8b64372.tar.gz linux-b5bdacf3bb027ba0af4d61b38ec289bfc8b64372.tar.bz2 linux-b5bdacf3bb027ba0af4d61b38ec289bfc8b64372.zip | |
net: Propagate lookup failure in l3mdev_get_saddr to caller
Commands run in a vrf context are not failing as expected on a route lookup:
root@kenny:~# ip ro ls table vrf-red
unreachable default
root@kenny:~# ping -I vrf-red -c1 -w1 10.100.1.254
ping: Warning: source address might be selected on device other than vrf-red.
PING 10.100.1.254 (10.100.1.254) from 0.0.0.0 vrf-red: 56(84) bytes of data.
--- 10.100.1.254 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms
Since the vrf table does not have a route for 10.100.1.254 the ping
should have failed. The saddr lookup causes a full VRF table lookup.
Propogating a lookup failure to the user allows the command to fail as
expected:
root@kenny:~# ping -I vrf-red -c1 -w1 10.100.1.254
connect: No route to host
Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/Kbuild')
0 files changed, 0 insertions, 0 deletions