From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com
Subject: Re: [PATCH bpf-next v3 00/12] s390/bpf: Implement arena
Date: Tue, 02 Jul 2024 16:40:35 +0000 [thread overview]
Message-ID: <171993843596.14841.16552310149645928981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240701234304.14336-1-iii@linux.ibm.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 2 Jul 2024 01:40:18 +0200 you wrote:
> v2: https://lore.kernel.org/bpf/20240701133432.3883-1-iii@linux.ibm.com/
> v2 -> v3: Fix bpf-gcc build issue.
>
> v1: https://lore.kernel.org/bpf/20240627090900.20017-1-iii@linux.ibm.com/
> v1 -> v2: Add a zero-extension fix.
> Fix wrong jump offset in the BPF_XCHG implementation.
> Do not run the UAF test on x86_64 and arm64.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,01/12] bpf: Fix atomic probe zero-extension
https://git.kernel.org/bpf/bpf-next/c/df34ec9db6f5
- [bpf-next,v3,02/12] s390/bpf: Factor out emitting probe nops
https://git.kernel.org/bpf/bpf-next/c/d0736d8c491d
- [bpf-next,v3,03/12] s390/bpf: Get rid of get_probe_mem_regno()
https://git.kernel.org/bpf/bpf-next/c/9a0485872691
- [bpf-next,v3,04/12] s390/bpf: Introduce pre- and post- probe functions
https://git.kernel.org/bpf/bpf-next/c/89b933a20137
- [bpf-next,v3,05/12] s390/bpf: Land on the next JITed instruction after exception
https://git.kernel.org/bpf/bpf-next/c/a1c04bcc41f9
- [bpf-next,v3,06/12] s390/bpf: Support BPF_PROBE_MEM32
https://git.kernel.org/bpf/bpf-next/c/4d3a453b434f
- [bpf-next,v3,07/12] s390/bpf: Support address space cast instruction
https://git.kernel.org/bpf/bpf-next/c/555469cc9be4
- [bpf-next,v3,08/12] s390/bpf: Enable arena
https://git.kernel.org/bpf/bpf-next/c/1e36027e39b8
- [bpf-next,v3,09/12] s390/bpf: Support arena atomics
https://git.kernel.org/bpf/bpf-next/c/2f9469484a3b
- [bpf-next,v3,10/12] selftests/bpf: Introduce __arena_global
https://git.kernel.org/bpf/bpf-next/c/b6349fd3448c
- [bpf-next,v3,11/12] selftests/bpf: Add UAF tests for arena atomics
https://git.kernel.org/bpf/bpf-next/c/490c99d4ed99
- [bpf-next,v3,12/12] selftests/bpf: Remove arena tests from DENYLIST.s390x
https://git.kernel.org/bpf/bpf-next/c/69716e44a74a
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:[~2024-07-02 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 23:40 [PATCH bpf-next v3 00/12] s390/bpf: Implement arena Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 01/12] bpf: Fix atomic probe zero-extension Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 02/12] s390/bpf: Factor out emitting probe nops Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 03/12] s390/bpf: Get rid of get_probe_mem_regno() Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 04/12] s390/bpf: Introduce pre- and post- probe functions Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 05/12] s390/bpf: Land on the next JITed instruction after exception Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 06/12] s390/bpf: Support BPF_PROBE_MEM32 Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 07/12] s390/bpf: Support address space cast instruction Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 08/12] s390/bpf: Enable arena Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 09/12] s390/bpf: Support arena atomics Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 10/12] selftests/bpf: Introduce __arena_global Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 11/12] selftests/bpf: Add UAF tests for arena atomics Ilya Leoshkevich
2024-07-01 23:40 ` [PATCH bpf-next v3 12/12] selftests/bpf: Remove arena tests from DENYLIST.s390x Ilya Leoshkevich
2024-07-02 16: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=171993843596.14841.16552310149645928981.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--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