From: John Fastabend <john.fastabend@gmail.com>
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org, borisp@nvidia.com, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
mykolal@fb.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, shuah@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, viro@zeniv.linux.org.uk,
mrpre@163.com
Subject: Re: [PATCH bpf-next v2 2/2] selftests/bpf: add ktls selftest
Date: Wed, 2 Apr 2025 16:49:37 -0700 [thread overview]
Message-ID: <20250402234937.riknwzpwdmly4byl@gmail.com> (raw)
In-Reply-To: <20250219052015.274405-3-jiayuan.chen@linux.dev>
On 2025-02-19 13:20:15, Jiayuan Chen wrote:
> add ktls selftest for sockmap
>
> Test results:
> sockmap_ktls/sockmap_ktls disconnect_after_delete IPv4 SOCKMAP:OK
> sockmap_ktls/sockmap_ktls update_fails_when_sock_has_ulp IPv4 SOCKMAP:OK
> sockmap_ktls/sockmap_ktls disconnect_after_delete IPv4 SOCKMAP:OK
> sockmap_ktls/sockmap_ktls update_fails_when_sock_has_ulp IPv4 SOCKMAP:OK
> sockmap_ktls/sockmap_ktls disconnect_after_delete IPv4 SOCKMAP:OK
> sockmap_ktls/sockmap_ktls update_fails_when_sock_has_ulp IPv4 SOCKMAP:OK
> sockmap_ktls/sockmap_ktls disconnect_after_delete IPv4 SOCKMAP:OK
> sockmap_ktls/sockmap_ktls update_fails_when_sock_has_ulp IPv4 SOCKMAP:OK
> sockmap_ktls/tls simple offload:OK
> sockmap_ktls/tls tx cork:OK
> sockmap_ktls/tls tx cork with push:OK
> sockmap_ktls/tls simple offload:OK
> sockmap_ktls/tls tx cork:OK
> sockmap_ktls/tls tx cork with push:OK
> sockmap_ktls:OK
>
> Signed-off-by: Jiayuan Chen <jiayuan.chen@linux.dev>
> ---
Thanks Jiayuan sorry for the _very_ long delay this fell of my list
and I missed it. Thanks again!
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2025-04-02 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 5:20 [PATCH bpf-next v2 0/2] bpf: fix ktls panic with sockmap and add tests Jiayuan Chen
2025-02-19 5:20 ` [PATCH bpf-next v2 1/2] bpf: fix ktls panic with sockmap Jiayuan Chen
2025-04-02 23:10 ` John Fastabend
2025-04-02 23:15 ` John Fastabend
2025-04-08 15:04 ` Jiayuan Chen
2025-02-19 5:20 ` [PATCH bpf-next v2 2/2] selftests/bpf: add ktls selftest Jiayuan Chen
2025-04-02 23:49 ` John Fastabend [this message]
2025-04-10 3:00 ` [PATCH bpf-next v2 0/2] bpf: fix ktls panic with sockmap and add tests 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=20250402234937.riknwzpwdmly4byl@gmail.com \
--to=john.fastabend@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=borisp@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mrpre@163.com \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yonghong.song@linux.dev \
/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