From: patchwork-bot+netdevbpf@kernel.org
To: Qiliang Yuan <odys.yuan@gmail.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, ihor.solodrai@linux.dev,
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, shuah@kernel.org,
void@manifault.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Run the cpumask map insert tests only for the test task
Date: Mon, 19 Oct 2026 03:20:06 +0000 [thread overview]
Message-ID: <179238000660.2381645.14989315546275364536.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009-selftests-bpf-cpumask-insert-filter-v1-1-3249218594d7@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Fri, 09 Oct 2026 09:49:32 +0800 you wrote:
> verify_success() attaches each cpumask test program to task_newtask,
> forks a single child, and expects err to be 0 afterwards. Most programs
> return right away for other tasks than the test one.
>
> test_insert_leave and test_insert_remove_release don't, and insert a
> cpumask into the single entry of __cpumask_map for every task created
> in the system while they are attached. test_insert_leave leaves its
> cpumask in the map, so a second task created, for instance by a test
> running in parallel, fails to insert one and sets err to 3. Two tasks
> created at the same time can do the same to test_insert_remove_release.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Run the cpumask map insert tests only for the test task
https://git.kernel.org/bpf/bpf-next/c/e2c978ad415c
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-10-19 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 1:49 [PATCH bpf-next] selftests/bpf: Run the cpumask map insert tests only for the test task Qiliang Yuan
2026-10-19 3:20 ` 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=179238000660.2381645.14989315546275364536.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=ihor.solodrai@linux.dev \
--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=odys.yuan@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=void@manifault.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.