public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: Yafang Shao <laoar.shao@gmail.com>, Jiri Olsa <jolsa@kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@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>,
	Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
	"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH bpf-next 1/3] bpf: Add support for bpf_get_func_ip helper for uprobe program
Date: Tue, 1 Aug 2023 12:44:46 -0700	[thread overview]
Message-ID: <20f1cf2e-6145-000a-0344-4c03c7b54e28@linux.dev> (raw)
In-Reply-To: <CALOAHbDdurfzh7jRfqWVVS5RFRT44fx3zjQRNN8B66HJDNogAQ@mail.gmail.com>



On 8/1/23 4:53 AM, Yafang Shao wrote:
> On Tue, Aug 1, 2023 at 3:30 PM Jiri Olsa <jolsa@kernel.org> wrote:
>>
>> Adding support for bpf_get_func_ip helper for uprobe program to return
>> probed address for both uprobe and return uprobe.
>>
>> We discussed this in [1] and agreed that uprobe can have special use
>> of bpf_get_func_ip helper that differs from kprobe.
>>
>> The kprobe bpf_get_func_ip returns:
>>    - address of the function if probe is attach on function entry
>>      for both kprobe and return kprobe
>>    - 0 if the probe is not attach on function entry
>>
>> The uprobe bpf_get_func_ip returns:
>>    - address of the probe for both uprobe and return uprobe
>>
>> The reason for this semantic change is that kernel can't really tell
>> if the probe user space address is function entry.
>>
>> The uprobe program is actually kprobe type program attached as uprobe.
>> One of the consequences of this design is that uprobes do not have its
>> own set of helpers, but share them with kprobes.
>>
>> As we need different functionality for bpf_get_func_ip helper for uprobe,
>> I'm adding the bool value to the bpf_trace_run_ctx, so the helper can
>> detect that it's executed in uprobe context and call specific code.
>>
>> The is_uprobe bool is set as true in bpf_prog_run_array_sleepable which
>> is currently used only for executing bpf programs in uprobe.
> 
> That is error-prone.  If we don't intend to rename
> bpf_prog_run_array_sleepable() to bpf_prog_run_array_uprobe(), I think
> we'd better introduce a new parameter 'bool is_uprobe' into it.

Agree that renaming bpf_prog_run_array_sleepable() to
bpf_prog_run_array_uprobe() probably better. This way, it is
self-explainable for `run_ctx.is_uprobe = true`.

If unlikely case in the future, another sleepable run prog array
is needed. They can have their own bpf_prog_run_array_<..>
and underlying bpf_prog_run_array_sleepable() can be factored out.

> 
>>
>> Suggested-by: Andrii Nakryiko <andrii@kernel.org>
>> [1] https://lore.kernel.org/bpf/CAEf4BzZ=xLVkG5eurEuvLU79wAMtwho7ReR+XJAgwhFF4M-7Cg@mail.gmail.com/
>> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
>> ---
>>   include/linux/bpf.h            |  5 +++++
>>   include/uapi/linux/bpf.h       |  7 ++++++-
>>   kernel/trace/bpf_trace.c       | 21 ++++++++++++++++++++-
>>   kernel/trace/trace_probe.h     |  5 +++++
>>   kernel/trace/trace_uprobe.c    |  5 -----
>>   tools/include/uapi/linux/bpf.h |  7 ++++++-
>>   6 files changed, 42 insertions(+), 8 deletions(-)
>>
>> diff --git a/include/linux/bpf.h b/include/linux/bpf.h
>> index ceaa8c23287f..8ea071383ef1 100644
>> --- a/include/linux/bpf.h
>> +++ b/include/linux/bpf.h
>> @@ -1819,6 +1819,7 @@ struct bpf_cg_run_ctx {
>>   struct bpf_trace_run_ctx {
>>          struct bpf_run_ctx run_ctx;
>>          u64 bpf_cookie;
>> +       bool is_uprobe;
>>   };
>>
>>   struct bpf_tramp_run_ctx {
>> @@ -1867,6 +1868,8 @@ bpf_prog_run_array(const struct bpf_prog_array *array,
>>          if (unlikely(!array))
>>                  return ret;
>>
>> +       run_ctx.is_uprobe = false;
>> +
>>          migrate_disable();
>>          old_run_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
>>          item = &array->items[0];
>> @@ -1906,6 +1909,8 @@ bpf_prog_run_array_sleepable(const struct bpf_prog_array __rcu *array_rcu,
>>          rcu_read_lock_trace();
>>          migrate_disable();
>>
>> +       run_ctx.is_uprobe = true;
>> +
>>          array = rcu_dereference_check(array_rcu, rcu_read_lock_trace_held());
>>          if (unlikely(!array))
>>                  goto out;
[...]

  reply	other threads:[~2023-08-01 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  7:29 [PATCH bpf-next 0/3] bpf: Support bpf_get_func_ip helper in uprobes Jiri Olsa
2023-08-01  7:30 ` [PATCH bpf-next 1/3] bpf: Add support for bpf_get_func_ip helper for uprobe program Jiri Olsa
2023-08-01 11:53   ` Yafang Shao
2023-08-01 19:44     ` Yonghong Song [this message]
2023-08-01 20:18       ` Yonghong Song
2023-08-01 20:43         ` Alexei Starovoitov
2023-08-02  7:15           ` Jiri Olsa
2023-08-02 11:21   ` Alan Maguire
2023-08-02 12:23     ` Jiri Olsa
2023-08-01  7:30 ` [PATCH bpf-next 2/3] selftests/bpf: Add bpf_get_func_ip tests for uprobe on function entry Jiri Olsa
2023-08-01  7:30 ` [PATCH bpf-next 3/3] selftests/bpf: Add bpf_get_func_ip test for uprobe inside function Jiri Olsa
2023-08-02 11:30   ` Alan Maguire
2023-08-02 12:26     ` Jiri Olsa
2023-08-02 12:42       ` Alan Maguire

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=20f1cf2e-6145-000a-0344-4c03c7b54e28@linux.dev \
    --to=yonghong.song@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=laoar.shao@gmail.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sdf@google.com \
    --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