mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: Hannes Laimer <h.laimer@proxmox.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
	David Ahern <dsahern@kernel.org>, Simon Horman <horms@kernel.org>,
	Shuah Khan <shuah@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 2/2] selftests: forwarding: vxlan_reserved: add gbp changelink test
Date: Mon, 26 Oct 2026 09:58:55 +0200	[thread overview]
Message-ID: <c561b8e2-40f3-48d4-8f2f-85b46163466b@blackwall.org> (raw)
In-Reply-To: <20261023-b4-vxlan-changelink-gbp-v1-2-f0d13951c09b@proxmox.com>

On 23/10/2026 14:14, Hannes Laimer wrote:
> On a device created with gbp, run the reserved bit probes before and
> after an unrelated changelink. Check that what the device accepts has
> not changed.
> 
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
>   tools/testing/selftests/net/forwarding/vxlan_reserved.sh | 15 +++++++++++++++
>   1 file changed, 15 insertions(+)
> 
> diff --git a/tools/testing/selftests/net/forwarding/vxlan_reserved.sh b/tools/testing/selftests/net/forwarding/vxlan_reserved.sh
> index 709845123727..0ce264cc57f8 100755
> --- a/tools/testing/selftests/net/forwarding/vxlan_reserved.sh
> +++ b/tools/testing/selftests/net/forwarding/vxlan_reserved.sh
> @@ -40,6 +40,7 @@
>   	reserved_31_test
>   	reserved_56_test
>   	reserved_63_test
> +	gbp_changelink_test
>       "}
>   
>   NUM_NETIFS=4
> @@ -338,6 +339,20 @@ reserved_63_test()
>   	    reserved_test 63
>   }
>   
> +gbp_changelink_test_do()
> +{
> +	vxlan_device_add gbp
> +	__default_test_do 25 "gbp"
> +	ip link set dev vx1 type vxlan ageing 300
> +	__default_test_do 25 "gbp after changelink"
> +}
> +
> +gbp_changelink_test()
> +{
> +	in_defer_scope \
> +	    gbp_changelink_test_do
> +}
> +
>   trap cleanup EXIT
>   
>   setup_prepare
> 

Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>


  reply	other threads:[~2026-10-26  7:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 11:14 [PATCH net 0/2] vxlan: keep reserved_bits on changelink Hannes Laimer
2026-10-23 11:14 ` [PATCH net 1/2] vxlan: keep reserved_bits across changelink Hannes Laimer
2026-10-26  7:58   ` Nikolay Aleksandrov
2026-10-26  9:52   ` Petr Machata
2026-10-23 11:14 ` [PATCH net 2/2] selftests: forwarding: vxlan_reserved: add gbp changelink test Hannes Laimer
2026-10-26  7:58   ` Nikolay Aleksandrov [this message]
2026-10-26  9:52   ` Petr Machata
2026-10-23 14:57 ` [PATCH net 0/2] vxlan: keep reserved_bits on changelink Gabriel Goller
2026-10-26  5:36 ` Hangbin Liu
2026-10-27 10:50 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c561b8e2-40f3-48d4-8f2f-85b46163466b@blackwall.org \
    --to=razor@blackwall.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@kernel.org \
    --cc=h.laimer@proxmox.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=shuah@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®