From: patchwork-bot+netdevbpf@kernel.org
To: Aleksei Oladko <aleksey.oladko@virtuozzo.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
petrm@nvidia.com, idosch@nvidia.com, nird@mellanox.com,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests: net: forwarding: fix IPv6 address leak in cleanup
Date: Sat, 07 Mar 2026 01:30:19 +0000 [thread overview]
Message-ID: <177284701954.117391.973842857088681580.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260305211000.515301-1-aleksey.oladko@virtuozzo.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Mar 2026 21:10:00 +0000 you wrote:
> Several forwarding tests (e.g., gre_multipath.sh) initialize both IPv4
> and IPv6 addresses using simple_if_init, but only clean up IPv4
> in simple_if_fini. This leaves stale IPv6 addresses on the interfaces,
> which causes subsequent tests to fail when they encounter unexpected
> address configuration.
>
> The issue can be reproduced by running tests in sequence:
> # run_kselftest.sh -t net/forwarding:ipip_hier_gre.sh
> # run_kselftest.sh -t net/forwarding:min_max_mtu.sh
> TAP version 13
> 1..1
> # timeout set to 0
> # selftests: net/forwarding: min_max_mtu.sh
> # TEST: ping [ OK ]
> # TEST: ping6 [ OK ]
> # TEST: Test maximum MTU configuration [ OK ]
> # TEST: Test traffic, packet size is maximum MTU [FAIL]
> # Ping6, packet size: 65487 succeeded, but should have failed
> # TEST: Test minimum MTU configuration [ OK ]
> # TEST: Test traffic, packet size is minimum MTU [ OK ]
> not ok 1 selftests: net/forwarding: min_max_mtu.sh # exit=1
>
> [...]
Here is the summary with links:
- [v2] selftests: net: forwarding: fix IPv6 address leak in cleanup
https://git.kernel.org/netdev/net-next/c/21c0dc7cdd07
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-07 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 21:10 [PATCH v2] selftests: net: forwarding: fix IPv6 address leak in cleanup Aleksei Oladko
2026-03-06 13:27 ` Ido Schimmel
2026-03-07 1:30 ` patchwork-bot+netdevbpf [this message]
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=177284701954.117391.973842857088681580.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksey.oladko@virtuozzo.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=nird@mellanox.com \
--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