public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Naveen Kumar Thummalapenta <naveen66@linux.ibm.com>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>, bpf@vger.kernel.org
Cc: skb99@linux.ibm.com, hbathini@linux.ibm.com,
	adubey@linux.ibm.com, ast@kernel.org,
	alexei.starovoitov@gmail.com, peterz@infradead.org,
	andrii@kernel.org, maddy@linux.ibm.com,
	linux-kernel@vger.kernel.org, riteshh@linux.ibm.com,
	alan.maguire@oracle.com
Subject: Re: [PATCH] bpf/selftests: remove test_access_variable_array
Date: Fri, 10 Apr 2026 22:51:56 +0530	[thread overview]
Message-ID: <8edf35db-c156-47ba-8f8d-1d269bb20cc3@linux.ibm.com> (raw)
In-Reply-To: <20260410105404.91126-1-venkat88@linux.ibm.com>


On 10/04/26 4:24 pm, Venkat Rao Bagalkote wrote:
> test_access_variable_array relied on accessing struct sched_domain::span
> to validate variable-length array handling via BTF. Recent scheduler
> refactoring removed or hid this field, causing the test
> to fail to build.
>
> Given that this test depends on internal scheduler structures that are
> subject to refactoring, and equivalent variable-length array coverage
> already exists via bpf_testmod-based tests, remove
> test_access_variable_array entirely.
>
> Link: https://lore.kernel.org/all/177434340048.1647592.8586759362906719839.tip-bot2@tip-bot2/
>
> Signed-off-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
> ---

Hi,

Tested this patch and it is fixing the build issue.


Without this patch:

progs/test_access_variable_array.c:14:13: error:
no member named 'span' in 'struct sched_domain'
     span = sd->span[0];
                ^~~~

With this patch above build is fixed

Please add below tag

Tested-by: Naveen Kumar Thummalapenta <naveen66@linux.ibm.com>

Regards,
Naveen Kumar T

>   .../bpf/prog_tests/access_variable_array.c    | 16 ----------------
>   .../bpf/progs/test_access_variable_array.c    | 19 -------------------
>   2 files changed, 35 deletions(-)
>   delete mode 100644 tools/testing/selftests/bpf/prog_tests/access_variable_array.c
>   delete mode 100644 tools/testing/selftests/bpf/progs/test_access_variable_array.c
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/access_variable_array.c b/tools/testing/selftests/bpf/prog_tests/access_variable_array.c
> deleted file mode 100644
> index 08131782437c..000000000000
> --- a/tools/testing/selftests/bpf/prog_tests/access_variable_array.c
> +++ /dev/null
> @@ -1,16 +0,0 @@
> -// SPDX-License-Identifier: GPL-2.0
> -/* Copyright (c) 2022 Bytedance */
> -
> -#include <test_progs.h>
> -#include "test_access_variable_array.skel.h"
> -
> -void test_access_variable_array(void)
> -{
> -	struct test_access_variable_array *skel;
> -
> -	skel = test_access_variable_array__open_and_load();
> -	if (!ASSERT_OK_PTR(skel, "test_access_variable_array__open_and_load"))
> -		return;
> -
> -	test_access_variable_array__destroy(skel);
> -}
> diff --git a/tools/testing/selftests/bpf/progs/test_access_variable_array.c b/tools/testing/selftests/bpf/progs/test_access_variable_array.c
> deleted file mode 100644
> index 326b7d1f496a..000000000000
> --- a/tools/testing/selftests/bpf/progs/test_access_variable_array.c
> +++ /dev/null
> @@ -1,19 +0,0 @@
> -// SPDX-License-Identifier: GPL-2.0
> -/* Copyright (c) 2023 Bytedance */
> -
> -#include "vmlinux.h"
> -#include <bpf/bpf_helpers.h>
> -#include <bpf/bpf_tracing.h>
> -
> -unsigned long span = 0;
> -
> -SEC("fentry/sched_balance_rq")
> -int BPF_PROG(fentry_fentry, int this_cpu, struct rq *this_rq,
> -		struct sched_domain *sd)
> -{
> -	span = sd->span[0];
> -
> -	return 0;
> -}
> -
> -char _license[] SEC("license") = "GPL";

  reply	other threads:[~2026-04-10 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 10:54 [PATCH] bpf/selftests: remove test_access_variable_array Venkat Rao Bagalkote
2026-04-10 17:21 ` Naveen Kumar Thummalapenta [this message]
2026-04-10 19:40 ` 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=8edf35db-c156-47ba-8f8d-1d269bb20cc3@linux.ibm.com \
    --to=naveen66@linux.ibm.com \
    --cc=adubey@linux.ibm.com \
    --cc=alan.maguire@oracle.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=hbathini@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maddy@linux.ibm.com \
    --cc=peterz@infradead.org \
    --cc=riteshh@linux.ibm.com \
    --cc=skb99@linux.ibm.com \
    --cc=venkat88@linux.ibm.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