From: patchwork-bot+netdevbpf@kernel.org
To: Leon Hwang <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
memxor@gmail.com, shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next 0/5] bpf: Follow-up fixes for BPF syscall common attributes
Date: Tue, 19 May 2026 02:00:10 +0000 [thread overview]
Message-ID: <177915601064.2051001.3397704272305322988.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260518145446.6794-1-leon.hwang@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 18 May 2026 22:54:41 +0800 you wrote:
> Address sashiko reviews for BPF syscall common attributes series.
>
> 1. The tailing padding bytes in struct bpf_common_attr should be
> checked. [1]
> 2. There was a concurrent regression in syscall.c::map_create(). [2]
> 3. OPTS_VALID() was missing to validate the nested struct bpf_log_opts
> in libbpf. [3]
> 4. The token_fd should be -1 to avoid a valid token fd in test. [4]
>
> [...]
Here is the summary with links:
- [bpf-next,1/5] bpf: Check tail zero of bpf_common_attr using offsetofend
https://git.kernel.org/bpf/bpf-next/c/f05ddc6771c4
- [bpf-next,2/5] bpf: Fix concurrent regression in map_create()
(no matching commit)
- [bpf-next,3/5] libbpf: Add OPTS_VALID() for log_opts in bpf_map_create
https://git.kernel.org/bpf/bpf-next/c/b4844cb6d1ec
- [bpf-next,4/5] selftests/bpf: Use -1 as token_fd in map create failure test
https://git.kernel.org/bpf/bpf-next/c/652f0c2c999d
- [bpf-next,5/5] selftests/bpf: Add test to verify checking padding bytes for BPF syscall common attributes
https://git.kernel.org/bpf/bpf-next/c/7732ad2412fd
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:[~2026-05-19 1:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 14:54 Leon Hwang
2026-05-18 14:54 ` [PATCH bpf-next 1/5] bpf: Check tail zero of bpf_common_attr using offsetofend Leon Hwang
2026-05-18 16:14 ` Mykyta Yatsenko
2026-05-19 2:45 ` Leon Hwang
2026-05-18 14:54 ` [PATCH bpf-next 2/5] bpf: Fix concurrent regression in map_create() Leon Hwang
2026-05-18 15:40 ` bot+bpf-ci
2026-05-19 2:48 ` Leon Hwang
2026-05-19 3:05 ` Alexei Starovoitov
2026-05-19 10:48 ` Leon Hwang
2026-05-18 16:43 ` Mykyta Yatsenko
2026-05-19 2:47 ` Leon Hwang
2026-05-19 15:15 ` Mykyta Yatsenko
2026-05-20 14:51 ` Leon Hwang
2026-05-18 14:54 ` [PATCH bpf-next 3/5] libbpf: Add OPTS_VALID() for log_opts in bpf_map_create Leon Hwang
2026-05-18 14:54 ` [PATCH bpf-next 4/5] selftests/bpf: Use -1 as token_fd in map create failure test Leon Hwang
2026-05-18 14:54 ` [PATCH bpf-next 5/5] selftests/bpf: Add test to verify checking padding bytes for BPF syscall common attributes Leon Hwang
2026-05-19 2:00 ` 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=177915601064.2051001.3397704272305322988.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-patches-bot@fb.com \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®