| 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
| ||
|
Message-ID: <20240509092257.2ecb8fd4@kernel.org> Date: Thu, 9 May 2024 09:22:57 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Taehee Yoo <ap420073@...il.com> Cc: davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com, shuah@...nel.org, netdev@...r.kernel.org, linux-kselftest@...r.kernel.org Subject: Re: [PATCH net] selftests: net: avoid waiting for server in amt.sh forever when it fails. On Wed, 8 May 2024 04:06:43 +0000 Taehee Yoo wrote: > In the forwarding testcase, it opens a server and a client with the nc. > The server receives the correct message from NC, it prints OK. > The server prints FAIL if it receives the wrong message from the client. > > But If the server can't receive any message, it will not close so > the amt.sh waits forever. > There are several reasons. > 1. crash of smcrouted. > 2. Send a message from the client to the server before the server is up. > > To avoid this problem, the server waits only for 10 seconds. > The client sends messages for 10 seconds. > If the server is successfully closed, it kills the client. Since this didn't fix the problem of smcroute crashing I had to take a closer look myself. I filed https://github.com/troglobit/smcroute/issues/207 for smcroute And sent: https://lore.kernel.org/all/20240509161919.3939966-1-kuba@kernel.org/ and https://lore.kernel.org/all/20240509161952.3940476-1-kuba@kernel.org/ Please don't use netcat in tests in the future. There are two incompatible implementations which always cause hard to repro issues.
Powered by blists - more mailing lists