From: Jiri Olsa <jolsa@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andriin@fb.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
"Martin KaFai Lau" <kafai@fb.com>,
"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"KP Singh" <kpsingh@chromium.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Julia Lawall" <julia.lawall@inria.fr>
Subject: [PATCHv4 bpf-next 0/5] bpf: Tracing and lsm programs re-attach
Date: Mon, 12 Apr 2021 18:24:57 +0200 [thread overview]
Message-ID: <20210412162502.1417018-1-jolsa@kernel.org> (raw)
hi,
while adding test for pinning the module while there's
trampoline attach to it, I noticed that we don't allow
link detach and following re-attach for trampolines.
Adding that for tracing and lsm programs.
You need to have patch [1] from bpf tree for test module
attach test to pass.
v4 changes:
- fix wrong cleanup goto jump reported by Julia
thanks,
jirka
[1] https://lore.kernel.org/bpf/20210326105900.151466-1-jolsa@kernel.org/
---
Jiri Olsa (5):
bpf: Allow trampoline re-attach for tracing and lsm programs
selftests/bpf: Add re-attach test to fentry_test
selftests/bpf: Add re-attach test to fexit_test
selftests/bpf: Add re-attach test to lsm test
selftests/bpf: Test that module can't be unloaded with attached trampoline
kernel/bpf/syscall.c | 23 +++++++++++++++++------
kernel/bpf/trampoline.c | 2 +-
tools/testing/selftests/bpf/prog_tests/fentry_test.c | 51 ++++++++++++++++++++++++++++++++++++---------------
tools/testing/selftests/bpf/prog_tests/fexit_test.c | 51 ++++++++++++++++++++++++++++++++++++---------------
tools/testing/selftests/bpf/prog_tests/module_attach.c | 23 +++++++++++++++++++++++
tools/testing/selftests/bpf/prog_tests/test_lsm.c | 48 ++++++++++++++++++++++++++++++++++++++----------
tools/testing/selftests/bpf/test_progs.h | 2 +-
7 files changed, 152 insertions(+), 48 deletions(-)
next reply other threads:[~2021-04-12 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 16:24 Jiri Olsa [this message]
2021-04-12 16:24 ` [PATCHv4 bpf-next 1/5] bpf: Allow trampoline re-attach for tracing and lsm programs Jiri Olsa
2021-04-13 22:03 ` Andrii Nakryiko
2021-04-14 11:01 ` Jiri Olsa
2021-04-12 16:24 ` [PATCHv4 bpf-next 2/5] selftests/bpf: Add re-attach test to fentry_test Jiri Olsa
2021-04-13 21:54 ` Andrii Nakryiko
2021-04-14 10:56 ` Jiri Olsa
2021-04-14 22:18 ` Andrii Nakryiko
2021-04-12 16:25 ` [PATCHv4 bpf-next 3/5] selftests/bpf: Add re-attach test to fexit_test Jiri Olsa
2021-04-13 21:55 ` Andrii Nakryiko
2021-04-14 11:01 ` Jiri Olsa
2021-04-12 16:25 ` [PATCHv4 bpf-next 4/5] selftests/bpf: Add re-attach test to lsm test Jiri Olsa
2021-04-13 21:57 ` Andrii Nakryiko
2021-04-14 10:54 ` Jiri Olsa
2021-04-12 16:25 ` [PATCHv4 bpf-next 5/5] selftests/bpf: Test that module can't be unloaded with attached trampoline Jiri Olsa
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=20210412162502.1417018-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=toke@redhat.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).