From: John Fastabend <john.fastabend@gmail.com>
To: zijianzhang@bytedance.com, bpf@vger.kernel.org
Cc: 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, mykolal@fb.com, shuah@kernel.org,
bhole_prashant_q7@lab.ntt.co.jp, jakub@cloudflare.com,
xiyou.wangcong@gmail.com, zijianzhang@bytedance.com
Subject: RE: [PATCH bpf 0/2] Two fixes for test_sockmap
Date: Wed, 16 Oct 2024 11:10:49 -0700 [thread overview]
Message-ID: <671001a983dd2_1e3420833@john.notmuch> (raw)
In-Reply-To: <20241012203731.1248619-1-zijianzhang@bytedance.com>
zijianzhang@ wrote:
> From: Zijian Zhang <zijianzhang@bytedance.com>
>
> Function msg_verify_data should have context of bytes_cnt and k instead of
> assuming they are zero. Otherwise, test_sockmap with data integrity test
> will report some errors. I also fix the logic related to size and index j
>
> 1/ 6 sockmap::txmsg test passthrough:FAIL
> 2/ 6 sockmap::txmsg test redirect:FAIL
> 7/12 sockmap::txmsg test apply:FAIL
> 10/11 sockmap::txmsg test push_data:FAIL
> 11/17 sockmap::txmsg test pull-data:FAIL
> 12/ 9 sockmap::txmsg test pop-data:FAIL
> 13/ 1 sockmap::txmsg test push/pop data:FAIL
> ...
> Pass: 24 Fail: 52
>
> After fixing msg_verify_data, some of the errors are solved, but for push
> pull and pop, we may need more fixes to msg_verify_data, added a TODO
>
> 10/11 sockmap::txmsg test push_data:FAIL
> 11/17 sockmap::txmsg test pull-data:FAIL
> 12/ 9 sockmap::txmsg test pop-data:FAIL
> ...
> Pass: 37 Fail: 15
Thanks. Did you plan on fixing the rest next? Otherwise I'll add it to
my list.
>
> Besides, added a custom errno EDATAINTEGRITY for msg_verify_data, we
> shall not ignore the error in txmsg_cork case, and fixed the txmsg_redir
> in test_txmsg_pull "Test pull + redirect" case.
>
>
> Zijian Zhang (2):
> selftests/bpf: Fix msg_verify_data in test_sockmap
> selftests/bpf: Fix txmsg_redir of test_txmsg_pull in test_sockmap
>
> tools/testing/selftests/bpf/test_sockmap.c | 32 ++++++++++++++--------
> 1 file changed, 21 insertions(+), 11 deletions(-)
>
> --
> 2.20.1
>
For the series,
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2024-10-16 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 20:37 [PATCH bpf 0/2] Two fixes for test_sockmap zijianzhang
2024-10-12 20:37 ` [PATCH bpf 1/2] selftests/bpf: Fix msg_verify_data in test_sockmap zijianzhang
2024-10-12 20:37 ` [PATCH bpf 2/2] selftests/bpf: Fix txmsg_redir of test_txmsg_pull " zijianzhang
2024-10-16 18:10 ` John Fastabend [this message]
2024-10-16 19:24 ` [PATCH bpf 0/2] Two fixes for test_sockmap Zijian Zhang
2024-10-16 20:50 ` 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=671001a983dd2_1e3420833@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bhole_prashant_q7@lab.ntt.co.jp \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jakub@cloudflare.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=xiyou.wangcong@gmail.com \
--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