linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcus Wichelmann <marcus.wichelmann@hetzner-cloud.de>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Jordan Rome <linux@jordanrome.com>,
	bpf@vger.kernel.org, linux-mm@kvack.org,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Kernel Team <kernel-team@fb.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Alexander Potapenko <glider@google.com>
Subject: Re: [bpf-next v8 3/3] selftests/bpf: Add tests for bpf_copy_from_user_task_str
Date: Sat, 22 Feb 2025 14:19:10 +0100	[thread overview]
Message-ID: <3fffc23d-45fa-497b-82a1-e09bb81c0011@hetzner-cloud.de> (raw)
In-Reply-To: <CAEf4BzYu9R0_0YghpXaE5-Ojds7W7eURyp+3BsaC4BHp=ZVszg@mail.gmail.com>

Am 21.02.25 um 19:26 schrieb Andrii Nakryiko:
> On Fri, Feb 21, 2025 at 7:01 AM Marcus Wichelmann
> <marcus.wichelmann@hetzner-cloud.de> wrote:
>>
>> Hi,
>>
>> I'm not sure what I'm doing wrong, but after rebasing on latest bpf-next
>> which includes this patch, I'm no longer able to build the bpf selftests:
>>
>> # pushd tools/testing/selftests/bpf/
>> # make -j80
>> [...]
>>     GEN-SKEL [test_progs] bpf_iter_task_vmas.skel.h
>>     CLNG-BPF [test_progs] bpf_iter_tasks.bpf.o
>> progs/bpf_iter_tasks.c:98:8: error: call to undeclared function 'bpf_copy_from_user_task_str'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>>      98 |         ret = bpf_copy_from_user_task_str((char *)task_str1, sizeof(task_str1), ptr, task, 0);
>>         |               ^
>> 1 error generated.
>> make: *** [Makefile:733: /root/linux/tools/testing/selftests/bpf/bpf_iter_tasks.bpf.o] Error 1
>>
>> I suppose the function definition should be in the vmlinux.h?
>>
> 
> Yes, it should be in vmlinux.h, and if you don't have it, then you
> must have a bit too old pahole.
> 
> $ git tag --contains ce4d0bc0200e3
> v1.27
> v1.28

Ah, my pahole version was 1.25. Compiling a newer version from source did the trick.
This was really the last thing I would have thought of.

Thank you very much for your help!

Marcus


  reply	other threads:[~2025-02-22 13:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 15:21 [bpf-next v8 1/3] mm: add copy_remote_vm_str Jordan Rome
2025-02-13 15:21 ` [bpf-next v8 2/3] bpf: Add bpf_copy_from_user_task_str kfunc Jordan Rome
2025-02-13 15:21 ` [bpf-next v8 3/3] selftests/bpf: Add tests for bpf_copy_from_user_task_str Jordan Rome
2025-02-21 15:00   ` Marcus Wichelmann
2025-02-21 18:26     ` Andrii Nakryiko
2025-02-22 13:19       ` Marcus Wichelmann [this message]
2025-02-19 23:33 ` [bpf-next v8 1/3] mm: add copy_remote_vm_str Shakeel Butt
2025-02-20  0:19   ` Andrew Morton
2025-02-20  1:02     ` Andrii Nakryiko
2025-02-20 11:22       ` Jordan Rome
2025-02-20  0:18 ` Andrew Morton
2025-02-20  1:02   ` Andrii Nakryiko
2025-02-20  1:20 ` 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=3fffc23d-45fa-497b-82a1-e09bb81c0011@hetzner-cloud.de \
    --to=marcus.wichelmann@hetzner-cloud.de \
    --cc=akpm@linux-foundation.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=glider@google.com \
    --cc=kernel-team@fb.com \
    --cc=linux-mm@kvack.org \
    --cc=linux@jordanrome.com \
    --cc=shakeel.butt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox