From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: patchwork-bot+netdevbpf@kernel.org
Cc: Ilya Leoshkevich <iii@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Walmsley <paul.walmsley@sifive.com>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v3 00/11] libbpf: Fix accessing syscall arguments
Date: Mon, 7 Feb 2022 08:10:11 -0800 [thread overview]
Message-ID: <CAEf4Bzb=YEGdDyB+8uFJ1OcSRVR11D9oqwJK=RYi9Jg+B2uhZw@mail.gmail.com> (raw)
In-Reply-To: <164409301110.21063.11730421603542210576.git-patchwork-notify@kernel.org>
On Sat, Feb 5, 2022 at 12:30 PM <patchwork-bot+netdevbpf@kernel.org> wrote:
>
> Hello:
>
> This series was applied to bpf/bpf-next.git (master)
> by Andrii Nakryiko <andrii@kernel.org>:
>
> On Fri, 4 Feb 2022 15:50:07 +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,v3,01/11] arm64/bpf: Add orig_x0 to user_pt_regs
> https://git.kernel.org/bpf/bpf-next/c/d473f4062165
> - [bpf-next,v3,02/11] s390/bpf: Add orig_gpr2 to user_pt_regs
> https://git.kernel.org/bpf/bpf-next/c/61f88e88f263
> - [bpf-next,v3,03/11] selftests/bpf: Fix an endianness issue in bpf_syscall_macro test
> https://git.kernel.org/bpf/bpf-next/c/a936c141cbe4
> - [bpf-next,v3,04/11] libbpf: Add __PT_PARM1_REG_SYSCALL macro
> https://git.kernel.org/bpf/bpf-next/c/3a9d84aafb8c
> - [bpf-next,v3,05/11] libbpf: Add PT_REGS_SYSCALL_REGS macro
> https://git.kernel.org/bpf/bpf-next/c/b62a862d42f5
> - [bpf-next,v3,06/11] selftests/bpf: Use PT_REGS_SYSCALL_REGS in bpf_syscall_macro
> https://git.kernel.org/bpf/bpf-next/c/730809c15ac2
> - [bpf-next,v3,07/11] libbpf: Fix accessing the first syscall argument on arm64
> https://git.kernel.org/bpf/bpf-next/c/8b9b06ad4726
> - [bpf-next,v3,08/11] libbpf: Fix accessing syscall arguments on powerpc
> https://git.kernel.org/bpf/bpf-next/c/f5af16d0ae28
> - [bpf-next,v3,09/11] libbpf: Fix accessing program counter on riscv
> https://git.kernel.org/bpf/bpf-next/c/27870c91b5c7
> - [bpf-next,v3,10/11] libbpf: Fix accessing syscall arguments on riscv
> https://git.kernel.org/bpf/bpf-next/c/5860b82236c6
> - [bpf-next,v3,11/11] libbpf: Fix accessing the first syscall argument on s390
> https://git.kernel.org/bpf/bpf-next/c/088d6aafd5bb
>
I've backed out this patch set from bpf-next for now while we are
deciding the best way to deal with s390x and arm64 arches without
breaking UAPIs.
> 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-07 16:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 14:50 [PATCH bpf-next v3 00/11] libbpf: Fix accessing syscall arguments Ilya Leoshkevich
2022-02-04 14:50 ` [PATCH bpf-next v3 01/11] arm64/bpf: Add orig_x0 to user_pt_regs Ilya Leoshkevich
2022-02-04 14:50 ` [PATCH bpf-next v3 02/11] s390/bpf: Add orig_gpr2 " Ilya Leoshkevich
2022-02-05 0:36 ` Heiko Carstens
2022-02-05 12:37 ` Vasily Gorbik
2022-02-04 14:50 ` [PATCH bpf-next v3 03/11] selftests/bpf: Fix an endianness issue in bpf_syscall_macro test Ilya Leoshkevich
2022-02-04 14:50 ` [PATCH bpf-next v3 04/11] libbpf: Add __PT_PARM1_REG_SYSCALL macro Ilya Leoshkevich
2022-02-04 16:15 ` Naveen N. Rao
2022-02-04 14:50 ` [PATCH bpf-next v3 05/11] libbpf: Add PT_REGS_SYSCALL_REGS macro Ilya Leoshkevich
2022-02-04 16:46 ` Naveen N. Rao
2022-02-04 18:15 ` Andrii Nakryiko
2022-02-05 7:04 ` Naveen N. Rao
2022-02-04 14:50 ` [PATCH bpf-next v3 06/11] selftests/bpf: Use PT_REGS_SYSCALL_REGS in bpf_syscall_macro Ilya Leoshkevich
2022-02-04 14:50 ` [PATCH bpf-next v3 07/11] libbpf: Fix accessing the first syscall argument on arm64 Ilya Leoshkevich
2022-02-04 14:50 ` [PATCH bpf-next v3 08/11] libbpf: Fix accessing syscall arguments on powerpc Ilya Leoshkevich
2022-02-05 7:05 ` Naveen N. Rao
2022-02-04 14:50 ` [PATCH bpf-next v3 09/11] libbpf: Fix accessing program counter on riscv Ilya Leoshkevich
2022-02-04 14:50 ` [PATCH bpf-next v3 10/11] libbpf: Fix accessing syscall arguments " Ilya Leoshkevich
2022-02-04 14:50 ` [PATCH bpf-next v3 11/11] libbpf: Fix accessing the first syscall argument on s390 Ilya Leoshkevich
2022-02-05 20:30 ` [PATCH bpf-next v3 00/11] libbpf: Fix accessing syscall arguments patchwork-bot+netdevbpf
2022-02-07 16:10 ` Andrii Nakryiko [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='CAEf4Bzb=YEGdDyB+8uFJ1OcSRVR11D9oqwJK=RYi9Jg+B2uhZw@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=ast@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=paul.walmsley@sifive.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;
as well as URLs for NNTP newsgroup(s).