Netdev List
 help / color / mirror / Atom feed
From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Geliang Tang <geliang@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Sabrina Dubroca <sd@queasysnail.net>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Shuah Khan <shuah@kernel.org>
Cc: Geliang Tang <tanggeliang@kylinos.cn>,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: tls: use ASSERT_GE in test_mutliproc
Date: Thu, 21 May 2026 18:57:32 +0800	[thread overview]
Message-ID: <5978f34d-dbcf-4196-8a95-13165a5ba034@linux.dev> (raw)
In-Reply-To: <0ee9f412b6bd1a260a547d19f979f73b396746ac.1779354585.git.tanggeliang@kylinos.cn>


On 5/21/26 5:11 PM, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> In test_mutliproc(), when send() or recv() returns an error (e.g.,
> -1), the test continues to execute the remaining code and fails
> repeatedly due to using EXPECT_GE.
>
> For example, if a TLS connection is broken and recv() returns -1,
> EXPECT_GE(res, 0) records a failure but does not stop the test.
> The test then proceeds with left -= res (where res = -1), causing
> left to increase unexpectedly, and the loop continues indefinitely.
>
> This results in a massive number of identical failure messages:
>
>   # tls.c:1686:mutliproc_sendpage_writers:Expected res (-1) >= 0 (0)
>   # tls.c:1686:mutliproc_sendpage_writers:Expected res (-1) >= 0 (0)
>   ... (hundreds of identical failures)

I think it’s worth backporting, so a Fixes tag is necessary.


> Fix this by replacing EXPECT_GE with ASSERT_GE. When send() or recv()
> fails, ASSERT_GE immediately aborts the current test, preventing
> the subsequent undefined behavior and endless failure messages.
>
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> ---
>   tools/testing/selftests/net/tls.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/net/tls.c b/tools/testing/selftests/net/tls.c
> index 30a236b8e9f7..9b9a3cb2700d 100644
> --- a/tools/testing/selftests/net/tls.c
> +++ b/tools/testing/selftests/net/tls.c
> @@ -1549,7 +1549,7 @@ test_mutliproc(struct __test_metadata *_metadata, struct _test_data_tls *self,
>   			res = recv(self->cfd, rb,
>   				   left > sizeof(rb) ? sizeof(rb) : left, 0);
>   
> -			EXPECT_GE(res, 0);
> +			ASSERT_GE(res, 0);
>   			left -= res;
>   		}
>   	} else {
> @@ -1566,7 +1566,7 @@ test_mutliproc(struct __test_metadata *_metadata, struct _test_data_tls *self,
>   				res = send(self->fd, buf,
>   					   left > file_sz ? file_sz : left, 0);
>   
> -			EXPECT_GE(res, 0);
> +			ASSERT_GE(res, 0);
>   			left -= res;
>   		}
>   	}

  reply	other threads:[~2026-05-21 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  9:11 [PATCH net-next] selftests: tls: use ASSERT_GE in test_mutliproc Geliang Tang
2026-05-21 10:57 ` Jiayuan Chen [this message]
2026-05-21 14:07   ` Jakub Kicinski
2026-05-21 14:20     ` Jiayuan Chen

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=5978f34d-dbcf-4196-8a95-13165a5ba034@linux.dev \
    --to=jiayuan.chen@linux.dev \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=shuah@kernel.org \
    --cc=tanggeliang@kylinos.cn \
    /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