From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii.nakryiko@gmail.com,
hca@linux.ibm.com, gor@linux.ibm.com, borntraeger@linux.ibm.com,
agordeev@linux.ibm.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v5 00/10] Fix accessing syscall arguments
Date: Wed, 09 Feb 2022 05:40:11 +0000 [thread overview]
Message-ID: <164438521198.19906.9141954700062717431.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220209021745.2215452-1-iii@linux.ibm.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 9 Feb 2022 03:17:35 +0100 you wrote:
> libbpf now has macros to access syscall arguments in an
> architecture-agnostic manner, but unfortunately they have a number of
> issues on non-Intel arches, which this series aims to fix.
>
> v1: https://lore.kernel.org/bpf/20220201234200.1836443-1-iii@linux.ibm.com/
> v1 -> v2:
> * Put orig_gpr2 in place of args[1] on s390 (Vasily).
> * Fix arm64, powerpc and riscv (Heiko).
>
> [...]
Here is the summary with links:
- [bpf-next,v5,01/10] selftests/bpf: Fix an endianness issue in bpf_syscall_macro test
https://git.kernel.org/bpf/bpf-next/c/4fc49b51ab9d
- [bpf-next,v5,02/10] libbpf: Add PT_REGS_SYSCALL_REGS macro
https://git.kernel.org/bpf/bpf-next/c/c5a1ffa0da76
- [bpf-next,v5,03/10] selftests/bpf: Use PT_REGS_SYSCALL_REGS in bpf_syscall_macro
https://git.kernel.org/bpf/bpf-next/c/3f928cab927c
- [bpf-next,v5,04/10] libbpf: Fix accessing syscall arguments on powerpc
https://git.kernel.org/bpf/bpf-next/c/f07f1503469b
- [bpf-next,v5,05/10] libbpf: Fix riscv register names
https://git.kernel.org/bpf/bpf-next/c/5c101153bfd6
- [bpf-next,v5,06/10] libbpf: Fix accessing syscall arguments on riscv
https://git.kernel.org/bpf/bpf-next/c/cf0b5b276923
- [bpf-next,v5,07/10] selftests/bpf: Skip test_bpf_syscall_macro:syscall_arg1 on arm64 and s390
https://git.kernel.org/bpf/bpf-next/c/9e45a377f29b
- [bpf-next,v5,08/10] libbpf: Allow overriding PT_REGS_PARM1{_CORE}_SYSCALL
https://git.kernel.org/bpf/bpf-next/c/60d16c5ccb81
- [bpf-next,v5,09/10] libbpf: Fix accessing the first syscall argument on arm64
https://git.kernel.org/bpf/bpf-next/c/fbca4a2f6497
- [bpf-next,v5,10/10] libbpf: Fix accessing the first syscall argument on s390
https://git.kernel.org/bpf/bpf-next/c/1f22a6f9f9a0
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:[~2022-02-09 5:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 2:17 [PATCH bpf-next v5 00/10] Fix accessing syscall arguments Ilya Leoshkevich
2022-02-09 2:17 ` [PATCH bpf-next v5 01/10] selftests/bpf: Fix an endianness issue in bpf_syscall_macro test Ilya Leoshkevich
2022-02-09 2:17 ` [PATCH bpf-next v5 02/10] libbpf: Add PT_REGS_SYSCALL_REGS macro Ilya Leoshkevich
2022-02-09 2:17 ` [PATCH bpf-next v5 03/10] selftests/bpf: Use PT_REGS_SYSCALL_REGS in bpf_syscall_macro Ilya Leoshkevich
2022-02-09 2:17 ` [PATCH bpf-next v5 04/10] libbpf: Fix accessing syscall arguments on powerpc Ilya Leoshkevich
2022-02-09 2:17 ` [PATCH bpf-next v5 05/10] libbpf: Fix riscv register names Ilya Leoshkevich
2022-02-09 2:17 ` [PATCH bpf-next v5 06/10] libbpf: Fix accessing syscall arguments on riscv Ilya Leoshkevich
2022-02-09 2:17 ` [PATCH bpf-next v5 07/10] selftests/bpf: Skip test_bpf_syscall_macro:syscall_arg1 on arm64 and s390 Ilya Leoshkevich
2022-02-09 2:17 ` [PATCH bpf-next v5 08/10] libbpf: Allow overriding PT_REGS_PARM1{_CORE}_SYSCALL Ilya Leoshkevich
2022-02-09 5:39 ` Andrii Nakryiko
2022-02-09 2:17 ` [PATCH bpf-next v5 09/10] libbpf: Fix accessing the first syscall argument on arm64 Ilya Leoshkevich
2022-02-09 5:39 ` Andrii Nakryiko
2022-02-09 2:17 ` [PATCH bpf-next v5 10/10] libbpf: Fix accessing the first syscall argument on s390 Ilya Leoshkevich
2022-02-09 5:39 ` Andrii Nakryiko
2022-02-09 5:39 ` [PATCH bpf-next v5 00/10] Fix accessing syscall arguments Andrii Nakryiko
2022-02-09 5:40 ` 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=164438521198.19906.9141954700062717431.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@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