From: patchwork-bot+netdevbpf@kernel.org
To: Zijian Zhang <zijianzhang@bytedance.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
mykolal@fb.com, shuah@kernel.org, jakub@cloudflare.com,
liujian56@huawei.com, cong.wang@bytedance.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next 0/8] Fixes to bpf_msg_push/pop_data and test_sockmap
Date: Thu, 07 Nov 2024 00:30:34 +0000 [thread overview]
Message-ID: <173093943451.1468976.4489026455212430103.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241106222520.527076-1-zijianzhang@bytedance.com>
Hello:
This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 6 Nov 2024 22:25:12 +0000 you wrote:
> From: Zijian Zhang <zijianzhang@bytedance.com>
>
> Several fixes to test_sockmap and added push/pop logic for msg_verify_data
> Before the fixes, some of the tests in test_sockmap are problematic,
> resulting in pseudo-correct result.
>
> 1. txmsg_pass is not set in some tests, as a result, no eBPF program is
> attached to the sockmap.
> 2. In SENDPAGE, a wrong iov_length in test_send_large may result in some
> test skippings and failures.
> 3. The calculation of total_bytes in msg_loop_rx is wrong, which may cause
> msg_loop_rx end early and skip some data tests.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/8] selftests/bpf: Add txmsg_pass to pull/push/pop in test_sockmap
https://git.kernel.org/bpf/bpf-next/c/66c54c20408d
- [v2,bpf-next,2/8] selftests/bpf: Fix SENDPAGE data logic in test_sockmap
https://git.kernel.org/bpf/bpf-next/c/4095031463d4
- [v2,bpf-next,3/8] selftests/bpf: Fix total_bytes in msg_loop_rx in test_sockmap
https://git.kernel.org/bpf/bpf-next/c/523dffccbade
- [v2,bpf-next,4/8] selftests/bpf: Add push/pop checking for msg_verify_data in test_sockmap
https://git.kernel.org/bpf/bpf-next/c/862087c3d362
- [v2,bpf-next,5/8] selftests/bpf: Add more tests for test_txmsg_push_pop in test_sockmap
https://git.kernel.org/bpf/bpf-next/c/47eae080410b
- [v2,bpf-next,6/8] bpf, sockmap: Several fixes to bpf_msg_push_data
https://git.kernel.org/bpf/bpf-next/c/15ab0548e310
- [v2,bpf-next,7/8] bpf, sockmap: Several fixes to bpf_msg_pop_data
https://git.kernel.org/bpf/bpf-next/c/5d609ba26247
- [v2,bpf-next,8/8] bpf, sockmap: Fix sk_msg_reset_curr
https://git.kernel.org/bpf/bpf-next/c/955afd57dc4b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-11-07 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 22:25 [PATCH v2 bpf-next 0/8] Fixes to bpf_msg_push/pop_data and test_sockmap zijianzhang
2024-11-06 22:25 ` [PATCH v2 bpf-next 1/8] selftests/bpf: Add txmsg_pass to pull/push/pop in test_sockmap zijianzhang
2024-11-06 22:25 ` [PATCH v2 bpf-next 2/8] selftests/bpf: Fix SENDPAGE data logic " zijianzhang
2024-11-06 22:25 ` [PATCH v2 bpf-next 3/8] selftests/bpf: Fix total_bytes in msg_loop_rx " zijianzhang
2024-11-06 22:25 ` [PATCH v2 bpf-next 4/8] selftests/bpf: Add push/pop checking for msg_verify_data " zijianzhang
2024-11-06 22:25 ` [PATCH v2 bpf-next 5/8] selftests/bpf: Add more tests for test_txmsg_push_pop " zijianzhang
2024-11-06 22:25 ` [PATCH v2 bpf-next 6/8] bpf, sockmap: Several fixes to bpf_msg_push_data zijianzhang
2024-11-06 22:25 ` [PATCH v2 bpf-next 7/8] bpf, sockmap: Several fixes to bpf_msg_pop_data zijianzhang
2024-11-06 22:25 ` [PATCH v2 bpf-next 8/8] bpf, sockmap: Fix sk_msg_reset_curr zijianzhang
2024-11-07 0:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 20:29 [PATCH v2 bpf-next 0/8] Fixes to bpf_msg_push/pop_data and test_sockmap zijianzhang
2024-11-06 19:31 ` Martin KaFai Lau
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=173093943451.1468976.4489026455212430103.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=liujian56@huawei.com \
--cc=martin.lau@linux.dev \
--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=yonghong.song@linux.dev \
--cc=zijianzhang@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox