From: Eduard Zingerman <eddyz87@gmail.com>
To: Haojian Zhuang <haojian.zhuang@linaro.org>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>
Subject: Re: [PATCH] bpf: check mem for dynptr type
Date: Mon, 04 Mar 2024 15:13:29 +0200 [thread overview]
Message-ID: <564df7e8c14864641c2f57a5283de53c746ea047.camel@gmail.com> (raw)
In-Reply-To: <ZeXGTP3ZIFRPGFCG@hackbox2.linaro.org>
On Mon, 2024-03-04 at 13:02 +0000, Haojian Zhuang wrote:
[...]
> Yes, I'm referring to bpf_user_ringbuf_drain() helper function.
>
> Yes, I should extend bpf/progs/user_ringbuf_success.c. And it could be
> loaded by bpf/prog_tests/user_ringbuf.c.
Before doing so, could you please share example you have in mind?
> But I failed to find the binary of user_ringbuf.c after bpf test cases
> built. And there're no binaries for the test cases in bpf/prog_tests
> directory. How to make use of these test cases? I failed to find
> documents on it. Could you help to share any tips to me? Thanks
The binary that runs tests is called "test_progs" and is compiled
using target "test_progs" under "tools/testing/selftests/bpf" directory.
Specific tests could be run using commands like:
- "./test_progs -a user_ringbuf" (to run all subtests in the group);
- "./test_progs -a user_ringbuf/test_user_ringbuf_loop"
(to run one subtest from the group).
I have an old writeup on setting up local testing environment,
if you need it I can update and share it.
next prev parent reply other threads:[~2024-03-04 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 2:37 [PATCH] bpf: check mem for dynptr type Haojian Zhuang
2024-03-04 12:46 ` Eduard Zingerman
2024-03-04 13:02 ` Haojian Zhuang
2024-03-04 13:13 ` Eduard Zingerman [this message]
2024-03-04 13:46 ` Haojian Zhuang
2024-03-04 17:08 ` Eduard Zingerman
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=564df7e8c14864641c2f57a5283de53c746ea047.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haojian.zhuang@linaro.org \
--cc=john.fastabend@gmail.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