public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Skorodumov <skorodumov.dmitry@huawei.com>
To: Paolo Abeni <pabeni@redhat.com>,
	Dmitry Skorodumov <dskr99@gmail.com>, <netdev@vger.kernel.org>,
	Simon Horman <horms@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-kselftest@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH net 2/2] selftests: net: simple selftest for ipvtap
Date: Tue, 30 Dec 2025 13:06:59 +0300	[thread overview]
Message-ID: <266e580a-9eeb-49d3-84cb-6d9fb62a165f@huawei.com> (raw)
In-Reply-To: <16fa929d-db04-48f5-a350-a31d23f8327c@redhat.com>


>> +test_ip_set_thread() {
>> +	ip link set ipvlan0 up
>> +	for ((i=0; i<IP_ITERATIONS; i++)); do
>> +		v=$(rnd)
>> +		ip a a "172.25.0.$v/24" dev ipvlan0 2>/dev/null
>> +		ip a a "fc00::$v/64" dev ipvlan0 2>/dev/null
>> +		v=$(rnd)
>> +		ip a d "172.25.0.$v/24" dev ipvlan0 2>/dev/null
>> +		ip a d "fc00::$v/64" dev ipvlan0 2>/dev/null
> It's unclear to me why the above tries to remove random addresses
> different from the ones just added (possibly not existing)

The idea is that we are trying to create conflicts between namespaces. If we add random address, and then delete the same address - nothing interesting happens. But if we delete some another random address - we will eventually occupy some share of IP-addresses - and conflicts start to appear. I'll mention this in comment in next version.


PS: I agree with other comments from your side. Will fix them.


Dmitry


      reply	other threads:[~2025-12-30 10:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251225185543.1459044-1-skorodumov.dmitry@huawei.com>
2025-12-25 18:55 ` [PATCH net 1/2] ipvlan: Make the addrs_lock be per port Dmitry Skorodumov
2025-12-28  9:46   ` Paolo Abeni
2025-12-25 18:55 ` [PATCH net 2/2] selftests: net: simple selftest for ipvtap Dmitry Skorodumov
2025-12-26 17:52   ` Stephen Hemminger
2025-12-28 12:14   ` Paolo Abeni
2025-12-30 10:06     ` Dmitry Skorodumov [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=266e580a-9eeb-49d3-84cb-6d9fb62a165f@huawei.com \
    --to=skorodumov.dmitry@huawei.com \
    --cc=davem@davemloft.net \
    --cc=dskr99@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --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=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