All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: bot+bpf-ci@kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	songliubraving@fb.com, yhs@fb.com, qmo@kernel.org,
	martin.lau@kernel.org, yonghong.song@linux.dev, clm@meta.com,
	ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next 2/3] selftests/bpf: Add tracing_multi link info tests
Date: Mon, 22 Jun 2026 12:36:06 +0200	[thread overview]
Message-ID: <ajkQFjlb94newiT1@krava> (raw)
In-Reply-To: <cb2607f92eea9b6470e906a22ad2148eda290f6f1389d6bebf155075566f5c33@mail.kernel.org>

On Sun, Jun 21, 2026 at 09:31:45PM +0000, bot+bpf-ci@kernel.org wrote:
> > diff --git a/tools/testing/selftests/bpf/prog_tests/fill_link_info.c b/tools/testing/selftests/bpf/prog_tests/fill_link_info.c
> > index f589eefbf9fb..969f04ee9ac6 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/fill_link_info.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/fill_link_info.c
> 
> [ ... ]
> 
> > @@ -396,6 +413,224 @@ static void test_kprobe_multi_fill_link_info(struct test_fill_link_info *skel,
> >  	bpf_link__destroy(link);
> >  }
> >
> > +static void verify_tracing_multi_invalid_user_buffer(int fd, const struct tmulti_target *targets)
> > +{
> > +	__u32 ids[TRACING_MULTI_CNT] = {};
> > +	struct bpf_link_info info;
> > +	__u32 len = sizeof(info);
> > +	int err, i;
> > +
> > +	/* Wrong info setup (ids != NULL and cnt == 0) -> EINVAL */
> > +	memset(&info, 0, sizeof(info));
> > +	info.tracing_multi.ids = ptr_to_u64(ids);
> > +	err = bpf_link_get_info_by_fd(fd, &info, &len);
> > +	ASSERT_EQ(err, -EINVAL, "tracing_multi.invalid_count");
> > +
> > +	/* Smaller than actuall count provided -> ENOSPC */
> 
> This isn't a bug, but "actuall" is misspelled here (should be "actual").
> 
> > +	memset(ids, 0, sizeof(ids));
> > +	memset(&info, 0, sizeof(info));
> > +	info.tracing_multi.ids = ptr_to_u64(ids);
> > +	info.tracing_multi.count = TRACING_MULTI_CNT - 1;
> > +	err = bpf_link_get_info_by_fd(fd, &info, &len);
> > +	ASSERT_EQ(err, -ENOSPC, "tracing_multi.small_count");
> > +	for (i = 0; i < TRACING_MULTI_CNT - 1; i++)
> > +		ASSERT_EQ(ids[i], targets[i].id, "tracing_multi.partial_ids");
> > +	/* check that the last entry is not populated */
> > +	ASSERT_EQ(ids[i], 0, "tracing_multi.partial_ids");
> > +
> > +	/* Bigger than actuall count provided -> OK */
> 
> The same typo appears here.

yep, will fix both

jirka

> 
> > +	memset(ids, 0, sizeof(ids));
> > +	memset(&info, 0, sizeof(info));
> > +	info.tracing_multi.ids = ptr_to_u64(ids);
> > +	info.tracing_multi.count = TRACING_MULTI_CNT + 1;
> > +	err = bpf_link_get_info_by_fd(fd, &info, &len);
> > +	ASSERT_OK(err, "tracing_multi.big_count");
> > +	for (i = 0; i < TRACING_MULTI_CNT; i++)
> > +		ASSERT_EQ(ids[i], targets[i].id, "tracing_multi.ids");
> 
> [ ... ]
> 
> 
> ---
> AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
> See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
> 
> CI run summary: https://github.com/kernel-patches/bpf/actions/runs/27917285330


  reply	other threads:[~2026-06-22 10:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-21 20:45 [PATCH bpf-next 0/3] bpf: tracing_multi link info support Jiri Olsa
2026-06-21 20:45 ` [PATCH bpf-next 1/3] bpf: Add " Jiri Olsa
2026-06-21 20:45 ` [PATCH bpf-next 2/3] selftests/bpf: Add tracing_multi link info tests Jiri Olsa
2026-06-21 20:53   ` sashiko-bot
2026-06-22 10:35     ` Jiri Olsa
2026-06-21 21:31   ` bot+bpf-ci
2026-06-22 10:36     ` Jiri Olsa [this message]
2026-06-21 20:45 ` [PATCH bpf-next 3/3] bpftool: Add tracing_multi link info output Jiri Olsa
2026-06-21 20:56   ` sashiko-bot
2026-06-22 10:35     ` Jiri Olsa

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=ajkQFjlb94newiT1@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bot+bpf-ci@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=clm@meta.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=martin.lau@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=qmo@kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    --cc=yonghong.song@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.