From: Yonghong Song <yhs@fb.com>
To: Song Chen <chensong_2000@189.cn>,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sample: bpf: syscall_tp_user: print result of verify_map
Date: Thu, 31 Mar 2022 20:01:52 -0700 [thread overview]
Message-ID: <882349c0-123d-3deb-88e8-d400ec702d1f@fb.com> (raw)
In-Reply-To: <1648777272-21473-1-git-send-email-chensong_2000@189.cn>
On 3/31/22 6:41 PM, Song Chen wrote:
> syscall_tp only prints the map id and messages when something goes wrong,
> but it doesn't print the value passed from bpf map. I think it's better
> to show that value to users.
>
> What's more, i also added a 2-second sleep before calling verify_map,
> to make the value more obvious.
>
> Signed-off-by: Song Chen <chensong_2000@189.cn>
> ---
> samples/bpf/syscall_tp_user.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/samples/bpf/syscall_tp_user.c b/samples/bpf/syscall_tp_user.c
> index a0ebf1833ed3..1faa7f08054e 100644
> --- a/samples/bpf/syscall_tp_user.c
> +++ b/samples/bpf/syscall_tp_user.c
> @@ -36,6 +36,9 @@ static void verify_map(int map_id)
> fprintf(stderr, "failed: map #%d returns value 0\n", map_id);
> return;
> }
> +
> + printf("verify map:%d val: %d\n", map_id, val);
I am not sure how useful it is or anybody really cares.
This is just a sample to demonstrate how bpf tracepoint works.
The error path has error print out already.
> +
> val = 0;
> if (bpf_map_update_elem(map_id, &key, &val, BPF_ANY) != 0) {
> fprintf(stderr, "map_update failed: %s\n", strerror(errno));
> @@ -98,6 +101,7 @@ static int test(char *filename, int num_progs)
> }
> close(fd);
>
> + sleep(2);
The commit message mentioned this sleep(2) is
to make the value more obvious. I don't know what does this mean.
sleep(2) can be added only if it fixed a bug.
> /* verify the map */
> for (i = 0; i < num_progs; i++) {
> verify_map(map0_fds[i]);
next prev parent reply other threads:[~2022-04-01 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 1:41 Song Chen
2022-04-01 3:01 ` Yonghong Song [this message]
2022-04-01 3:37 ` Song Chen
2022-04-01 16:28 ` Yonghong Song
2022-04-02 2:38 ` Song Chen
2022-04-02 3:37 Song Chen
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=882349c0-123d-3deb-88e8-d400ec702d1f@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chensong_2000@189.cn \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.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
all inboxes | Powered by JetHome®