From: Jiri Olsa <jolsa@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrii Nakryiko <andrii@kernel.org>,
Tianyi Liu <i.pear@outlook.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: bpf@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH bpf-next 0/2] selftests/bpf: Add uprobe pid filter test
Date: Thu, 29 Aug 2024 21:45:03 +0200 [thread overview]
Message-ID: <20240829194505.402807-1-jolsa@kernel.org> (raw)
hi,
in response to [1] patch, I'm adding bpf selftest that confirms the
change fixes problem for bpf programs trigered by return uprobe created
over perf event.
Oleg pointed out other issues with uprobe_multi pid filter,
I plan to send another patchset for that.
thanks,
jirka
[1] https://lore.kernel.org/linux-trace-kernel/ME0P300MB0416034322B9915ECD3888649D882@ME0P300MB0416.AUSP300.PROD.OUTLOOK.COM/
---
Jiri Olsa (2):
selftests/bpf: Add child argument to spawn_child function
selftests/bpf: Add uprobe pid filter test for multiple processes
tools/testing/selftests/bpf/prog_tests/uprobe_multi_test.c | 188 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------
tools/testing/selftests/bpf/progs/uprobe_multi_pid_filter.c | 61 ++++++++++++++++++++++++++++++
2 files changed, 203 insertions(+), 46 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/uprobe_multi_pid_filter.c
next reply other threads:[~2024-08-29 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 19:45 Jiri Olsa [this message]
2024-08-29 19:45 ` [PATCH bpf-next 1/2] selftests/bpf: Add child argument to spawn_child function Jiri Olsa
2024-08-29 19:45 ` [PATCH bpf-next 2/2] selftests/bpf: Add uprobe pid filter test for multiple processes Jiri Olsa
2024-08-30 20:51 ` Andrii Nakryiko
2024-08-30 17:08 ` [PATCH bpf-next 0/2] selftests/bpf: Add uprobe pid filter test Stanislav Fomichev
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=20240829194505.402807-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=i.pear@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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).