From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
memxor@gmail.com
Subject: Re: [PATCH bpf-next v2] selftests/bpf: Fix map_kptr test failure
Date: Fri, 16 Jan 2026 23:00:08 +0000 [thread overview]
Message-ID: <176860440829.828763.15143009427668744208.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260116052245.3692405-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 15 Jan 2026 21:22:45 -0800 you wrote:
> On my arm64 machine, I get the following failure:
> ...
> tester_init:PASS:tester_log_buf 0 nsec
> process_subtest:PASS:obj_open_mem 0 nsec
> process_subtest:PASS:specs_alloc 0 nsec
> serial_test_map_kptr:PASS:rcu_tasks_trace_gp__open_and_load 0 nsec
> ...
> test_map_kptr_success:PASS:map_kptr__open_and_load 0 nsec
> test_map_kptr_success:PASS:test_map_kptr_ref1 refcount 0 nsec
> test_map_kptr_success:FAIL:test_map_kptr_ref1 retval unexpected error: 2 (errno 2)
> test_map_kptr_success:PASS:test_map_kptr_ref2 refcount 0 nsec
> test_map_kptr_success:FAIL:test_map_kptr_ref2 retval unexpected error: 1 (errno 2)
> ...
> #201/21 map_kptr/success-map:FAIL
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: Fix map_kptr test failure
https://git.kernel.org/bpf/bpf-next/c/efad162f5a84
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-01-16 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 5:22 [PATCH bpf-next v2] selftests/bpf: Fix map_kptr test failure Yonghong Song
2026-01-16 7:34 ` Kumar Kartikeya Dwivedi
2026-01-16 23: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=176860440829.828763.15143009427668744208.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=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.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