All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Ihor Solodrai <ihor.solodrai@linux.dev>,
	Alexei Starovoitov <ast@kernel.org>,
	 Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Kumar Kartikeya Dwivedi	 <memxor@gmail.com>,
	Quentin Monnet <qmo@kernel.org>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v1 4/4] selftests/bpf: Check that sorting preserves types in bpftool dump
Date: Thu, 20 Aug 2026 13:42:04 -0700	[thread overview]
Message-ID: <6a0a841f4b41032cf69f5ba7d80189cfe7f4c4ab.camel@gmail.com> (raw)
In-Reply-To: <20260820000627.3826188-5-ihor.solodrai@linux.dev>

On Wed, 2026-08-19 at 17:06 -0700, Ihor Solodrai wrote:

...

> @@ -87,6 +90,36 @@ static struct btf *mk_btf(void)
>  	if (!ASSERT_OK(err, "holey_tail"))
>  		goto err_out;
>  
> +	for (i = 0; i < 3; i++) {

Testing this locally, a single enum suffices to showcase the bug,
why the complication?

> +		char name[16];
> +
> +		snprintf(name, sizeof(name), "E%d", i);
> +
> +		id = btf__add_enum(btf, NULL, 4);
> +		if (!ASSERT_GT(id, 0, "anon_enum"))
> +			goto err_out;
> +
> +		err = btf__add_enum_value(btf, name, i + 1);
> +		if (!ASSERT_OK(err, "enum_val"))
> +			goto err_out;
> +	}
> +
> +	id = btf__add_struct(btf, "s", 4);
> +	if (!ASSERT_GT(id, 0, "struct_s"))
> +		goto err_out;
> +
> +	err = btf__add_field(btf, "f", 1, 0, 0);
> +	if (!ASSERT_OK(err, "s_field"))
> +		goto err_out;
> +
> +	id = btf__add_union(btf, "u", 4);
> +	if (!ASSERT_GT(id, 0, "union_u"))
> +		goto err_out;
> +
> +	err = btf__add_field(btf, "f", 1, 0, 0);
> +	if (!ASSERT_OK(err, "u_field"))
> +		goto err_out;
> +
>  	btf__set_pointer_size(btf, 4);
>  
>  	return btf;
> @@ -95,6 +128,42 @@ static struct btf *mk_btf(void)

...

> +static void test_sort_preserves_types(const char *path)
> +{
> +	char *sorted = NULL, *unsorted = NULL;
> +	int n_sorted, n_unsorted;
> +
> +	sorted = dump_c(path, true);
> +	unsorted = dump_c(path, false);
> +	if (!sorted || !unsorted)
> +		goto out;
> +
> +	/*
> +	 * Count definitions by the closing brace in their first column. Counting
> +	 * "struct"/"union"/"enum" openers instead would also count forward
> +	 * declarations, and which types need one depends on emission order.
> +	 */
> +	n_unsorted = count_substr(unsorted, "\n}");
> +	n_sorted = count_substr(sorted, "\n}");

This does not include e.g. typedef. I'd just match for presence of enum.
Or better yet, compare full expected output with actual one and tailor
several BTF definitions, each for a specific sub-test.

> +	ASSERT_GT(n_unsorted, 0, "types_emitted");
> +	ASSERT_EQ(n_sorted, n_unsorted, "same_type_count");
> +
> +out:
> +	free(sorted);
> +	free(unsorted);
> +}
> +
>  /*
>   * Check only what the selftests build cannot:
>   *   - bpf_helpers.h defines __ksym and __weak as well, and no program uses

...

  reply	other threads:[~2026-08-20 20:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  0:06 [PATCH bpf-next v1 0/4] bpftool, selftests: Add tests for C dump and fix a dropped type Ihor Solodrai
2026-08-20  0:06 ` [PATCH bpf-next v1 1/4] selftests/bpf: NUL-terminate bpftool command output Ihor Solodrai
2026-08-20 18:43   ` Eduard Zingerman
2026-08-20  0:06 ` [PATCH bpf-next v1 2/4] selftests/bpf: Add tests for bpftool btf dump format c Ihor Solodrai
2026-08-20  0:16   ` sashiko-bot
2026-08-20  0:51   ` bot+bpf-ci
2026-08-20 19:09   ` Eduard Zingerman
2026-08-20 21:01     ` Ihor Solodrai
2026-08-20  0:06 ` [PATCH bpf-next v1 3/4] bpftool: Don't drop a type in the sorted C dump Ihor Solodrai
2026-08-20 20:47   ` Eduard Zingerman
2026-08-21  0:18   ` Andrii Nakryiko
2026-08-20  0:06 ` [PATCH bpf-next v1 4/4] selftests/bpf: Check that sorting preserves types in bpftool dump Ihor Solodrai
2026-08-20 20:42   ` Eduard Zingerman [this message]
2026-08-20 20:58     ` Ihor Solodrai
2026-08-20 21:25       ` 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=6a0a841f4b41032cf69f5ba7d80189cfe7f4c4ab.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=ihor.solodrai@linux.dev \
    --cc=memxor@gmail.com \
    --cc=qmo@kernel.org \
    /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.