From: Martin KaFai Lau <martin.lau@linux.dev>
To: zijianzhang@bytedance.com
Cc: daniel@iogearbox.net, john.fastabend@gmail.com, ast@kernel.org,
andrii@kernel.org, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
mykolal@fb.com, shuah@kernel.org, jakub@cloudflare.com,
liujian56@huawei.com, cong.wang@bytedance.com,
John Fastabend <john.fastabend@gmail.com>,
bpf@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next 0/8] Fixes to bpf_msg_push/pop_data and test_sockmap
Date: Wed, 6 Nov 2024 11:31:26 -0800 [thread overview]
Message-ID: <047c7b32-8b69-4816-bf8b-dba0b806ec93@linux.dev> (raw)
In-Reply-To: <20241024202917.3443231-1-zijianzhang@bytedance.com>
On 10/24/24 1:29 PM, zijianzhang@bytedance.com 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.
>
> Besides, for msg_verify_data, I added push/pop checking logic to function
> msg_verify_data and added more tests for different cases.
>
> After that, I found that there are some bugs in bpf_msg_push_data,
> bpf_msg_pop_data and sk_msg_reset_curr, and fix them. I guess the reason
> why they have not been exposed is that because of the above problems, they
> will not be triggered.
>
> With the fixes, we can pass the sockmap test with data integrity test now.
> However, the fixes to test_sockmap expose more problems in sockhash test
> with SENDPAGE and ktls with SENDPAGE.
Please carry over the Reviewed-by tag from John and usually you should cc the
reviewers in the new revision.
Please respin and tag with "bpf-next". Thanks for reporting the CI failed to
apply issue on v1. The bpf CI has been fixed to automatically try the
bpf-next/net branch after failing to apply to the default bpf-next/master branch.
pw-bot: cr
next prev parent reply other threads:[~2024-11-06 19:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 20:29 [PATCH v2 bpf-next 0/8] Fixes to bpf_msg_push/pop_data and test_sockmap zijianzhang
2024-10-24 20:29 ` [PATCH v2 bpf-next 1/8] selftests/bpf: Add txmsg_pass to pull/push/pop in test_sockmap zijianzhang
2024-10-24 20:29 ` [PATCH v2 bpf-next 2/8] selftests/bpf: Fix SENDPAGE data logic " zijianzhang
2024-10-24 20:29 ` [PATCH v2 bpf-next 3/8] selftests/bpf: Fix total_bytes in msg_loop_rx " zijianzhang
2024-10-24 20:29 ` [PATCH v2 bpf-next 4/8] selftests/bpf: Add push/pop checking for msg_verify_data " zijianzhang
2024-10-24 20:29 ` [PATCH v2 bpf-next 5/8] selftests/bpf: Add more tests for test_txmsg_push_pop " zijianzhang
2024-10-24 20:29 ` [PATCH v2 bpf-next 6/8] bpf, sockmap: Several fixes to bpf_msg_push_data zijianzhang
2024-10-24 20:29 ` [PATCH v2 bpf-next 7/8] bpf, sockmap: Several fixes to bpf_msg_pop_data zijianzhang
2024-10-24 20:29 ` [PATCH v2 bpf-next 8/8] bpf, sockmap: Fix sk_msg_reset_curr zijianzhang
2024-11-06 19:31 ` Martin KaFai Lau [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-06 22:25 [PATCH v2 bpf-next 0/8] Fixes to bpf_msg_push/pop_data and test_sockmap zijianzhang
2024-11-07 0:30 ` 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=047c7b32-8b69-4816-bf8b-dba0b806ec93@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--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=mykolal@fb.com \
--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