From: Lior Ribak <liorribak@gmail.com>
To: yhs@fb.com
Cc: andriin@fb.com, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com, kafai@fb.com,
kpsingh@chromium.org, liorribak@gmail.com, songliubraving@fb.com
Subject: Re: [PATCH] samples/bpf: Support both enter and exit kprobes in helper
Date: Sat, 22 Aug 2020 04:27:13 -0700 [thread overview]
Message-ID: <20200822112713.317226-1-liorribak@gmail.com> (raw)
In-Reply-To: <99122200-5308-25c0-cc4f-145847ef7edb@fb.com>
On 8/15/20 11:02 PM, Yonghong Song wrote:
>On 8/15/20 12:57 PM, Lior Ribak wrote:
>> Currently, in bpf_load.c, the function write_kprobe_events sets
>> the function name to probe as the probe name.
>> Even though it's valid to set one kprobe on enter and another on exit,
>> bpf_load.c won't handle it, and will return an error 'File exists'.
>>
>> Add a prefix to the event name to indicate if it's on enter or exit,
>> so both an enter and an exit kprobes can be attached.
>
>Only bpf_load.c change and no users here. So do you imply that
>use use this piece code in your own environment some how? But in
>that case, not sure whether this patch is necessary or not.
>
>The change here is for legacy bpf_load which may go away in the future.
>I understand this is for debugfs based kprobe_events where current
>libbpf does not support. But if possible, you should upgrade to use
>fd-based kprobe which is introduced roughly in/around 4.17 and libbpf
>has proper support.
I used the samples and it's toolchain to write my own bpf, so i wrote this
patch to save the trouble to the next one who will try to register 2
kprobes on the same function.
I still suggest to apply the patch because it solves a bug.
As I see it, all the wrappers around ebpf are duplicated everywhere, and
fd-based krpobe is already wrapped in the bcc project, so if you suggest
to switch and use it, maybe it's better to import some of the code from
bcc instead
>
>>
>> Signed-off-by: Lior Ribak <liorribak@gmail.com>
>> ---
>> samples/bpf/bpf_load.c | 20 +++++++++++++-------
>> 1 file changed, 13 insertions(+), 7 deletions(-)
>>
>> diff --git a/samples/bpf/bpf_load.c b/samples/bpf/bpf_load.c
>> index c5ad528f046e..69102358e91a 100644
>> --- a/samples/bpf/bpf_load.c
>> +++ b/samples/bpf/bpf_load.c
>> @@ -184,18 +184,24 @@ static int load_and_attach(const char *event, struct bpf_insn *prog, int size)
>>
>> #ifdef __x86_64__
>> if (strncmp(event, "sys_", 4) == 0) {
>> - snprintf(buf, sizeof(buf), "%c:__x64_%s __x64_%s",
>> - is_kprobe ? 'p' : 'r', event, event);
>> + if (is_kprobe)
>> + event_prefix = "__x64_enter_";
>> + else
>> + event_prefix = "__x64_exit_";
>> + snprintf(buf, sizeof(buf), "%c:%s%s __x64_%s",
>> + is_kprobe ? 'p' : 'r', event_prefix, event, event);
>> err = write_kprobe_events(buf);
>> - if (err >= 0) {
>> + if (err >= 0)
>> need_normal_check = false;
>> - event_prefix = "__x64_";
>> - }
>> }
>> #endif
>> if (need_normal_check) {
>> - snprintf(buf, sizeof(buf), "%c:%s %s",
>> - is_kprobe ? 'p' : 'r', event, event);
>> + if (is_kprobe)
>> + event_prefix = "enter_";
>> + else
>> + event_prefix = "exit_";
>> + snprintf(buf, sizeof(buf), "%c:%s%s %s",
>> + is_kprobe ? 'p' : 'r', event_prefix, event, event);
>> err = write_kprobe_events(buf);
>> if (err < 0) {
>> printf("failed to create kprobe '%s' error '%s'\n",
>>
next prev parent reply other threads:[~2020-08-22 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 19:57 [PATCH] samples/bpf: Support both enter and exit kprobes in helper Lior Ribak
2020-08-16 6:02 ` Yonghong Song
2020-08-22 11:27 ` Lior Ribak [this message]
2020-08-22 16:00 ` Andrii Nakryiko
-- strict thread matches above, loose matches on Subject: below --
2020-08-15 19:56 Lior Ribak
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=20200822112713.317226-1-liorribak@gmail.com \
--to=liorribak@gmail.com \
--cc=andriin@fb.com \
--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=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