From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
sdf@google.com, haoluo@google.com, alan.maguire@oracle.com
Subject: Re: [PATCHv2 bpf-next 0/2] bpf: Add check for negative uprobe multi offset
Date: Mon, 18 Dec 2023 18:10:23 +0000 [thread overview]
Message-ID: <170292302389.20983.13395967238198421768.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231217215538.3361991-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sun, 17 Dec 2023 22:55:36 +0100 you wrote:
> hi,
> adding the check for negative offset for uprobe multi link.
>
> v2 changes:
> - add more failure checks [Alan]
> - move the offset retrieval/check up in the loop to be done earlier [Song]
>
> [...]
Here is the summary with links:
- [PATCHv2,bpf-next,1/2] bpf: Fail uprobe multi link with negative offset
https://git.kernel.org/bpf/bpf-next/c/3983c00281d9
- [PATCHv2,bpf-next,2/2] selftests/bpf: Add more uprobe multi fail tests
https://git.kernel.org/bpf/bpf-next/c/f17d1a18a3dd
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-12-18 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 21:55 [PATCHv2 bpf-next 0/2] bpf: Add check for negative uprobe multi offset Jiri Olsa
2023-12-17 21:55 ` [PATCHv2 bpf-next 1/2] bpf: Fail uprobe multi link with negative offset Jiri Olsa
2023-12-18 16:12 ` Song Liu
2023-12-18 17:56 ` Andrii Nakryiko
2023-12-19 8:33 ` Jiri Olsa
2023-12-17 21:55 ` [PATCHv2 bpf-next 2/2] selftests/bpf: Add more uprobe multi fail tests Jiri Olsa
2023-12-18 16:19 ` Song Liu
2023-12-18 17:53 ` Andrii Nakryiko
2023-12-18 18:10 ` 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=170292302389.20983.13395967238198421768.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.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