From: patchwork-bot+netdevbpf@kernel.org
To: Tao Chen <chen.dylane@linux.dev>
Cc: song@kernel.org, jolsa@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, laoar.shao@gmail.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 1/2] bpf: Check link_create parameter for multi_kprobe
Date: Wed, 09 Apr 2025 23:40:52 +0000 [thread overview]
Message-ID: <174424205228.3077267.12250129138735203026.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250407035752.1108927-1-chen.dylane@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 7 Apr 2025 11:57:51 +0800 you wrote:
> The flags in link_create no used in multi_kprobe, return -EINVAL if
> they assigned, keep it same as other link attach apis. Perhaps due to
> their usage habits, users may set the target_fd to -1. Therefore, no
> check is carried out here, and it is kept consistent with the multi_uprobe.
>
> Fixes: 0dcac2725406 ("bpf: Add multi kprobe link")
> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Check link_create parameter for multi_kprobe
https://git.kernel.org/bpf/bpf-next/c/243911982aa9
- [bpf-next,v2,2/2] bpf: Check link_create parameter for multi_uprobe
https://git.kernel.org/bpf/bpf-next/c/a76116f422c4
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:[~2025-04-09 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 3:57 [PATCH bpf-next v2 1/2] bpf: Check link_create parameter for multi_kprobe Tao Chen
2025-04-07 3:57 ` [PATCH bpf-next v2 2/2] bpf: Check link_create parameter for multi_uprobe Tao Chen
2025-04-09 23:40 ` 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=174424205228.3077267.12250129138735203026.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=chen.dylane@linux.dev \
--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=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=song@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;
as well as URLs for NNTP newsgroup(s).