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: <ZVSQ9y37zobubeN+@Laptop-X1>
Date: Wed, 15 Nov 2023 17:35:51 +0800
From: Hangbin Liu <liuhangbin@...il.com>
To: Paolo Abeni <pabeni@...hat.com>
Cc: David Ahern <dsahern@...nel.org>,
	Stephen Hemminger <stephen@...workplumber.org>,
	netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
	Jakub Kicinski <kuba@...nel.org>,
	Eric Dumazet <edumazet@...gle.com>, Shuah Khan <shuah@...nel.org>,
	linux-kselftest@...r.kernel.org,
	Po-Hsu Lin <po-hsu.lin@...onical.com>,
	Guillaume Nault <gnault@...hat.com>
Subject: Re: [Discuss] Seeking advice on net selftests netns naming method

On Wed, Nov 15, 2023 at 10:10:38AM +0100, Paolo Abeni wrote:
> > Thanks, this is a good idea. I reviewed all the test cases and it should works
> > for most of them. Only the SRv6 tests are a little complex as they use 2 id
> > number for netns name. e.g. the setup_hs() in
> > srv6_end_dt46_l3vpn_test.sh. I plan to add the tmp string between the hs/rt and
> > ids. e.g. hs-xxxxxx-t100-1, rt-xxxxxx-1. I will have a try first.
> 
> Supposing netns_init() creates a namespace named <unique>, I think the
> following (very hackish thing) would work:
> 
> # create an alias for the namespace
> ln -s /var/run/netns/<unique> /var/run/netns/hs-t${tid}-${hs}

We can't do this as the purpose of using "unique" namespace name is do
Parallel testing. If we create the soft link and run multi SRv6 tests (there
are multi SRv6 tests with same netns name) at the same time, the naming will
be conflict.

Thanks
Hangbin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ