All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jiayuan Chen" <jiayuan.chen@linux.dev>
To: "Ihor Solodrai" <ihor.solodrai@linux.dev>,
	ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, kuba@kernel.org,
	pabeni@redhat.com, mykolal@fb.com, kernel-team@meta.com
Subject: Re: [PATCH bpf] selftests/bpf: mitigate sockmap_ktls disconnect_after_delete failure
Date: Wed, 16 Apr 2025 17:39:45 +0000	[thread overview]
Message-ID: <edd05a3ce17ed40c179a076750261f02cb3e314e@linux.dev> (raw)
In-Reply-To: <20250416170246.2438524-1-ihor.solodrai@linux.dev>

April 17, 2025 at 01:02, "Ihor Solodrai" <ihor.solodrai@linux.dev> wrote:

> 
> "sockmap_ktls disconnect_after_delete" test has been failing on BPF CI
> 
> after recent merges from netdev:
> 
> * https://github.com/kernel-patches/bpf/actions/runs/14458537639
> 
> * https://github.com/kernel-patches/bpf/actions/runs/14457178732
> 
> It happens because disconnect has been disabled for TLS [1], and it
> 
> renders the test case invalid.
> 
> Removing all the test code creates a conflict between bpf and
> 
> bpf-next, so for now only remove the offending assert [2].
> 
> The test will be removed later on bpf-next.
> 
> [1] https://lore.kernel.org/netdev/20250404180334.3224206-1-kuba@kernel.org/
> 
> [2] https://lore.kernel.org/bpf/cfc371285323e1a3f3b006bfcf74e6cf7ad65258@linux.dev/
> 
> Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>

Reviewed-by: Jiayuan Chen <jiayuan.chen@linux.dev>

Thanks.

> ---
> 
>  tools/testing/selftests/bpf/prog_tests/sockmap_ktls.c | 1 -
> 
>  1 file changed, 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/bpf/prog_tests/sockmap_ktls.c b/tools/testing/selftests/bpf/prog_tests/sockmap_ktls.c
> 
> index 2d0796314862..0a99fd404f6d 100644
> 
> --- a/tools/testing/selftests/bpf/prog_tests/sockmap_ktls.c
> 
> +++ b/tools/testing/selftests/bpf/prog_tests/sockmap_ktls.c
> 
> @@ -68,7 +68,6 @@ static void test_sockmap_ktls_disconnect_after_delete(int family, int map)
> 
>  goto close_cli;
> 
>  
> 
>  err = disconnect(cli);
> 
> - ASSERT_OK(err, "disconnect");
> 
>  
> 
>  close_cli:
> 
>  close(cli);
> 
> -- 
> 
> 2.49.0
>

  reply	other threads:[~2025-04-16 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 17:02 [PATCH bpf] selftests/bpf: mitigate sockmap_ktls disconnect_after_delete failure Ihor Solodrai
2025-04-16 17:39 ` Jiayuan Chen [this message]
2025-04-16 21:20 ` patchwork-bot+netdevbpf

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=edd05a3ce17ed40c179a076750261f02cb3e314e@linux.dev \
    --to=jiayuan.chen@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.