From: patchwork-bot+netdevbpf@kernel.org
To: Tyrone Wu <wudevelops@gmail.com>
Cc: andrii.nakryiko@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
haoluo@google.com, john.fastabend@gmail.com, jolsa@kernel.org,
kernel-patches-bot@fb.com, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, martin.lau@linux.dev,
mathieu.desnoyers@efficios.com, mattbobrowski@google.com,
mhiramat@kernel.org, mykolal@fb.com, rostedt@goodmis.org,
sdf@fomichev.me, shuah@kernel.org, song@kernel.org,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf v2 1/2] bpf: fix unpopulated path_size when uprobe_multi fields unset
Date: Fri, 11 Oct 2024 02:20:27 +0000 [thread overview]
Message-ID: <172861322701.2249999.15080735852713427254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241011000803.681190-1-wudevelops@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 11 Oct 2024 00:08:02 +0000 you wrote:
> Previously when retrieving `bpf_link_info.uprobe_multi` with `path` and
> `path_size` fields unset, the `path_size` field is not populated
> (remains 0). This behavior was inconsistent with how other input/output
> string buffer fields work, as the field should be populated in cases
> when:
> - both buffer and length are set (currently works as expected)
> - both buffer and length are unset (not working as expected)
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] bpf: fix unpopulated path_size when uprobe_multi fields unset
https://git.kernel.org/bpf/bpf/c/ad6b5b6ea9b7
- [bpf,v2,2/2] selftests/bpf: assert link info uprobe_multi count & path_size if unset
https://git.kernel.org/bpf/bpf/c/b836cbdf3b81
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:[~2024-10-11 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 22:06 [PATCH bpf v1 1/2] bpf: fix unpopulated path_size when uprobe_multi fields unset Tyrone Wu
2024-10-09 22:06 ` [PATCH bpf v1 2/2] selftests/bpf: assert link info uprobe_multi count & path_size if unset Tyrone Wu
2024-10-10 22:01 ` Andrii Nakryiko
2024-10-11 0:08 ` [PATCH bpf v2 1/2] bpf: fix unpopulated path_size when uprobe_multi fields unset Tyrone Wu
2024-10-11 0:08 ` [PATCH bpf v2 2/2] selftests/bpf: assert link info uprobe_multi count & path_size if unset Tyrone Wu
2024-10-11 2: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=172861322701.2249999.15080735852713427254.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-patches-bot@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mattbobrowski@google.com \
--cc=mhiramat@kernel.org \
--cc=mykolal@fb.com \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=wudevelops@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