From: "Toke Høiland-Jørgensen" <toke@redhat•com>
To: Jiri Olsa <jolsa@kernel•org>, 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>
Subject: Re: [PATCHv2 bpf-next 1/5] bpf: Allow trampoline re-attach for tracing and lsm programs
Date: Tue, 06 Apr 2021 23:35:14 +0200 [thread overview]
Message-ID: <87tuoj2j1p.fsf@toke.dk> (raw)
In-Reply-To: <20210406212913.970917-2-jolsa@kernel.org>
Jiri Olsa <jolsa@kernel•org> writes:
> Currently we don't allow re-attaching of trampolines. Once
> it's detached, it can't be re-attach even when the program
> is still loaded.
>
> Adding the possibility to re-attach the loaded tracing and
> lsm programs.
>
> Signed-off-by: Jiri Olsa <jolsa@kernel•org>
Acked-by: Toke Høiland-Jørgensen <toke@redhat•com>
next prev parent reply other threads:[~2021-04-06 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 21:29 [PATCHv2 bpf-next 0/5] bpf: Tracing and lsm programs re-attach Jiri Olsa
2021-04-06 21:29 ` [PATCHv2 bpf-next 1/5] bpf: Allow trampoline re-attach for tracing and lsm programs Jiri Olsa
2021-04-06 21:35 ` Toke Høiland-Jørgensen [this message]
2021-04-06 21:29 ` [PATCHv2 bpf-next 2/5] selftests/bpf: Add re-attach test to fentry_test Jiri Olsa
2021-04-07 22:47 ` Andrii Nakryiko
2021-04-08 11:52 ` Jiri Olsa
2021-04-06 21:29 ` [PATCHv2 bpf-next 3/5] selftests/bpf: Add re-attach test to fexit_test Jiri Olsa
2021-04-07 22:51 ` Andrii Nakryiko
2021-04-08 11:51 ` Jiri Olsa
2021-04-06 21:29 ` [PATCHv2 bpf-next 4/5] selftests/bpf: Add re-attach test to lsm test Jiri Olsa
2021-04-06 21:29 ` [PATCHv2 bpf-next 5/5] selftests/bpf: Test that module can't be unloaded with attached trampoline Jiri Olsa
2021-04-07 23:04 ` Andrii Nakryiko
2021-04-08 11:59 ` 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=87tuoj2j1p.fsf@toke.dk \
--to=toke@redhat$(echo .)com \
--cc=andriin@fb$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=john.fastabend@gmail$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kafai@fb$(echo .)com \
--cc=kpsingh@chromium$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=songliubraving@fb$(echo .)com \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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