From: patchwork-bot+netdevbpf@kernel.org
To: Feng Yang <yangfeng59949@163.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
daniel@iogearbox.net, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 bpf-next 0/5] selftests/bpf: Fix several issues in test_progs.c
Date: Fri, 24 Jul 2026 21:33:14 +0000 [thread overview]
Message-ID: <178492879488.3315717.16767263989748199323.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260723085100.482147-1-yangfeng59949@163.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Thu, 23 Jul 2026 16:50:55 +0800 you wrote:
> From: Feng Yang <yangfeng@kylinos.cn>
>
> Fix several issues in test_progs.c
>
> v3: Add fix incorrect error checking for pthread_create patch
> Memory allocation null checks for the worker logic are relatively complex;
> remove them for now and submit them separately in a follow-up patch.
>
> [...]
Here is the summary with links:
- [v3,bpf-next,1/5] selftests/bpf: Fix double free of subtest_state->name
https://git.kernel.org/bpf/bpf-next/c/791841e038c4
- [v3,bpf-next,2/5] selftests/bpf: Fix incorrect error checking for pthread_create
https://git.kernel.org/bpf/bpf-next/c/b04b8d4e198a
- [v3,bpf-next,3/5] selftests/bpf: Fix missing allocation null checks in test_progs.c
https://git.kernel.org/bpf/bpf-next/c/12b362b2f06b
- [v3,bpf-next,4/5] selftests/bpf: Use calloc to allocate subtest_states
https://git.kernel.org/bpf/bpf-next/c/a813ad2185cd
- [v3,bpf-next,5/5] selftests/bpf: Fix memory leak on subtest_states reallocation
https://git.kernel.org/bpf/bpf-next/c/06efb01c6530
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-07-24 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 8:50 [PATCH v3 bpf-next 0/5] selftests/bpf: Fix several issues in test_progs.c Feng Yang
2026-07-23 8:50 ` [PATCH v3 bpf-next 1/5] selftests/bpf: Fix double free of subtest_state->name Feng Yang
2026-07-23 8:50 ` [PATCH v3 bpf-next 2/5] selftests/bpf: Fix incorrect error checking for pthread_create Feng Yang
2026-07-23 8:50 ` [PATCH v3 bpf-next 3/5] selftests/bpf: Fix missing allocation null checks in test_progs.c Feng Yang
2026-07-23 9:17 ` sashiko-bot
2026-07-24 7:32 ` Feng Yang
2026-07-23 8:50 ` [PATCH v3 bpf-next 4/5] selftests/bpf: Use calloc to allocate subtest_states Feng Yang
2026-07-23 8:51 ` [PATCH v3 bpf-next 5/5] selftests/bpf: Fix memory leak on subtest_states reallocation Feng Yang
2026-07-24 21:33 ` 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=178492879488.3315717.16767263989748199323.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=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=yangfeng59949@163.com \
--cc=yonghong.song@linux.dev \
/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