From: patchwork-bot+netdevbpf@kernel.org
To: Manu Bretelle <chantr4@gmail.com>
Cc: mykolal@fb.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
shuah@kernel.org, xukuohai@huawei.com, eddyz87@gmail.com,
bpf@vger.kernel.org
Subject: Re: [PATCH] selftests/bpf: Reset err when symbol name already exist in kprobe_multi_test
Date: Mon, 10 Apr 2023 16:50:17 +0000 [thread overview]
Message-ID: <168114541756.32510.13001527318099007411.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230408022919.54601-1-chantr4@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 7 Apr 2023 19:29:19 -0700 you wrote:
> When trying to add a name to the hashmap, an error code of EEXIST is
> returned and we continue as names are possibly duplicated in the sys
> file.
>
> If the last name in the file is a duplicate, we will continue to the
> next iteration of the while loop, and exit the loop with a value of err
> set to EEXIST and enter the error label with err set, which causes the
> test to fail when it should not.
>
> [...]
Here is the summary with links:
- selftests/bpf: Reset err when symbol name already exist in kprobe_multi_test
https://git.kernel.org/bpf/bpf-next/c/c4d3b488a90b
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:[~2023-04-10 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 2:29 [PATCH] selftests/bpf: Reset err when symbol name already exist in kprobe_multi_test Manu Bretelle
2023-04-10 16:50 ` 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=168114541756.32510.13001527318099007411.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=chantr4@gmail.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=xukuohai@huawei.com \
--cc=yhs@fb.com \
/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;
as well as URLs for NNTP newsgroup(s).