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
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix flaky test btf_map_in_map/lookup_update
Date: Mon, 25 Mar 2024 16:30:32 +0000 [thread overview]
Message-ID: <171138423231.22247.17992219697516714017.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240322061353.632136-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 21 Mar 2024 23:13:53 -0700 you wrote:
> Recently, I frequently hit the following test failure:
>
> [root@arch-fb-vm1 bpf]# ./test_progs -n 33/1
> test_lookup_update:PASS:skel_open 0 nsec
> ...
> test_lookup_update:PASS:sync_rcu 0 nsec
> test_lookup_update:FAIL:map1_leak inner_map1 leaked!
> #33/1 btf_map_in_map/lookup_update:FAIL
> #33 btf_map_in_map:FAIL
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Fix flaky test btf_map_in_map/lookup_update
https://git.kernel.org/bpf/bpf-next/c/14bb1e8c8d4a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-03-25 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 6:13 [PATCH bpf-next] selftests/bpf: Fix flaky test btf_map_in_map/lookup_update Yonghong Song
2024-03-25 16:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-22 5:07 Yonghong Song
2024-03-22 14:25 ` Yonghong Song
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=171138423231.22247.17992219697516714017.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=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