From: patchwork-bot+netdevbpf@kernel.org
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, dxu@dxuuu.xyz,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org, andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next v2] selftests/bpf: Fix build of task_pt_regs test for arm64
Date: Tue, 07 Sep 2021 15:30:05 +0000 [thread overview]
Message-ID: <163102860559.11849.11862203994349641299.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210906163635.302307-1-jean-philippe@linaro.org>
Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Mon, 6 Sep 2021 17:36:38 +0100 you wrote:
> struct pt_regs is not exported to userspace on all archs. arm64 and s390
> export "user_pt_regs" instead, which causes build failure at the moment:
>
> progs/test_task_pt_regs.c:8:16: error: variable has incomplete type 'struct pt_regs'
> struct pt_regs current_regs = {};
>
> Instead of using pt_regs from ptrace.h, use the larger kernel struct
> from vmlinux.h directly. Since the test runner task_pt_regs.c does not
> have access to the kernel struct definition, copy it into a char array.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: Fix build of task_pt_regs test for arm64
https://git.kernel.org/bpf/bpf/c/3a029e1f3d6e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-09-07 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 16:36 [PATCH bpf-next v2] selftests/bpf: Fix build of task_pt_regs test for arm64 Jean-Philippe Brucker
2021-09-07 10:26 ` Ilya Leoshkevich
2021-09-07 15:30 ` patchwork-bot+netdevbpf [this message]
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=163102860559.11849.11862203994349641299.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=jean-philippe@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@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