[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180307.133959.164143912162200448.davem@davemloft.net>
Date: Wed, 07 Mar 2018 13:39:59 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: sbrivio@...hat.com
Cc: dsahern@...il.com, weiwan@...gle.com, yoshfuji@...ux-ipv6.org,
maze@...gle.com, xmu@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3] selftests: net: Introduce first PMTU test
From: Stefano Brivio <sbrivio@...hat.com>
Date: Tue, 6 Mar 2018 22:16:27 +0100
> One single test implemented so far: test_pmtu_vti6_exception
> checks that the PMTU of a route exception, caused by a tunnel
> exceeding the link layer MTU, is affected by administrative
> changes of the tunnel MTU. Creation of the route exception is
> checked too.
>
> Requested-by: David Ahern <dsahern@...il.com>
> Signed-off-by: Stefano Brivio <sbrivio@...hat.com>
> ---
> v3: Explicitly set veth MTU before causing route exception to ensure we actually
> decrease the PMTU as second step in the test (issue reported by David Ahern)
>
> v2: Fix error handling for setup_*() functions, make 'ip route get' output
> parsing more robust, sleep after configuring vti6 addresses (all issues
> reported by David Ahern)
Applied.
Powered by blists - more mailing lists