linux-kernel - Re: [PATCH net 2/2] selftests: net: simple selftest for ipvtap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <266e580a-9eeb-49d3-84cb-6d9fb62a165f@huawei.com>
Date: Tue, 30 Dec 2025 13:06:59 +0300
From: Dmitry Skorodumov <skorodumov.dmitry@...wei.com>
To: Paolo Abeni <pabeni@...hat.com>, Dmitry Skorodumov <dskr99@...il.com>,
	<netdev@...r.kernel.org>, Simon Horman <horms@...nel.org>,
	<linux-kernel@...r.kernel.org>, <linux-kselftest@...r.kernel.org>
CC: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
	<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Shuah Khan
	<shuah@...nel.org>
Subject: Re: [PATCH net 2/2] selftests: net: simple selftest for ipvtap


>> +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