From: Jiri Olsa <jolsa@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
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: [RFC bpf-next] bpf: Use prog->active instead of bpf_prog_active for kprobe_multi
Date: Wed, 25 May 2022 13:40:03 +0200 [thread overview]
Message-ID: <20220525114003.61890-1-jolsa@kernel.org> (raw)
hi,
Alexei suggested to use prog->active instead global bpf_prog_active
for programs attached with kprobe multi [1].
AFAICS this will bypass bpf_disable_instrumentation, which seems to be
ok for some places like hash map update, but I'm not sure about other
places, hence this is RFC post.
I'm not sure how are kprobes different to trampolines in this regard,
because trampolines use prog->active and it's not a problem.
thoughts?
thanks,
jirka
[1] https://lore.kernel.org/bpf/20220316185333.ytyh5irdftjcklk6@ast-mbp.dhcp.thefacebook.com/
---
kernel/trace/bpf_trace.c | 31 +++++++++++++++++++------------
1 file changed, 19 insertions(+), 12 deletions(-)
diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
index 10b157a6d73e..7aec39ae0a1c 100644
--- a/kernel/trace/bpf_trace.c
+++ b/kernel/trace/bpf_trace.c
@@ -2385,8 +2385,8 @@ static u64 bpf_kprobe_multi_entry_ip(struct bpf_run_ctx *ctx)
}
static int
-kprobe_multi_link_prog_run(struct bpf_kprobe_multi_link *link,
- unsigned long entry_ip, struct pt_regs *regs)
+__kprobe_multi_link_prog_run(struct bpf_kprobe_multi_link *link,
+ unsigned long entry_ip, struct pt_regs *regs)
{
struct bpf_kprobe_multi_run_ctx run_ctx = {
.link = link,
@@ -2395,21 +2395,28 @@ kprobe_multi_link_prog_run(struct bpf_kprobe_multi_link *link,
struct bpf_run_ctx *old_run_ctx;
int err;
- if (unlikely(__this_cpu_inc_return(bpf_prog_active) != 1)) {
- err = 0;
- goto out;
- }
-
- migrate_disable();
- rcu_read_lock();
old_run_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
err = bpf_prog_run(link->link.prog, regs);
bpf_reset_run_ctx(old_run_ctx);
+ return err;
+}
+
+static int
+kprobe_multi_link_prog_run(struct bpf_kprobe_multi_link *link,
+ unsigned long entry_ip, struct pt_regs *regs)
+{
+ struct bpf_prog *prog = link->link.prog;
+ int err = 0;
+
+ migrate_disable();
+ rcu_read_lock();
+
+ if (likely(__this_cpu_inc_return(*(prog->active)) == 1))
+ err = __kprobe_multi_link_prog_run(link, entry_ip, regs);
+
+ __this_cpu_dec(*(prog->active));
rcu_read_unlock();
migrate_enable();
-
- out:
- __this_cpu_dec(bpf_prog_active);
return err;
}
--
2.35.3
next reply other threads:[~2022-05-25 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 11:40 Jiri Olsa [this message]
2022-05-26 16:23 ` [RFC bpf-next] bpf: Use prog->active instead of bpf_prog_active for kprobe_multi Yonghong Song
2022-05-31 23:24 ` Andrii Nakryiko
2022-06-08 4:29 ` Alexei Starovoitov
2022-06-08 12:32 ` Jiri Olsa
2022-06-09 18:26 ` Andrii Nakryiko
2022-06-09 22:03 ` Alexei Starovoitov
2022-06-10 17:58 ` Andrii Nakryiko
2022-06-11 20:53 ` Alexei Starovoitov
2022-06-13 12:36 ` Jiri Olsa
2022-06-13 16:32 ` Andrii Nakryiko
2022-06-13 16:38 ` Andrii Nakryiko
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=20220525114003.61890-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).