From: Yafang Shao <laoar.shao@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, quentin@isovalent.com, rostedt@goodmis.org,
mhiramat@kernel.org, bpf@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v6 bpf-next 05/11] bpf: Clear the probe_addr for uprobe
Date: Wed, 5 Jul 2023 18:00:54 +0800 [thread overview]
Message-ID: <CALOAHbDs1L4Pot4-M0g4b9uSCwZgQYb1SQZ-QqAdxvZGLdW0uw@mail.gmail.com> (raw)
In-Reply-To: <5ed6bc64-ab80-486b-fb13-207174d9ff2d@iogearbox.net>
On Wed, Jul 5, 2023 at 4:19 PM Daniel Borkmann <daniel@iogearbox.net> wrote:
>
> On 6/28/23 1:53 PM, Yafang Shao wrote:
> > To avoid returning uninitialized or random values when querying the file
> > descriptor (fd) and accessing probe_addr, it is necessary to clear the
> > variable prior to its use.
> >
> > Fixes: 41bdc4b40ed6 ("bpf: introduce bpf subcommand BPF_TASK_FD_QUERY")
> > Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> > Acked-by: Yonghong Song <yhs@fb.com>
> > ---
> > kernel/trace/bpf_trace.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
> > index 1f9f78e1992f..ac9958907a7c 100644
> > --- a/kernel/trace/bpf_trace.c
> > +++ b/kernel/trace/bpf_trace.c
> > @@ -2382,10 +2382,12 @@ int bpf_get_perf_event_info(const struct perf_event *event, u32 *prog_id,
> > event->attr.type == PERF_TYPE_TRACEPOINT);
> > #endif
> > #ifdef CONFIG_UPROBE_EVENTS
> > - if (flags & TRACE_EVENT_FL_UPROBE)
> > + if (flags & TRACE_EVENT_FL_UPROBE) {
> > err = bpf_get_uprobe_info(event, fd_type, buf,
> > probe_offset,
> > event->attr.type == PERF_TYPE_TRACEPOINT);
> > + *probe_addr = 0x0;
> > + }
>
> Could we make this a bit more robust by just moving the zero'ing into the common path?
Agree. Will change it.
>
> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
> index 03b7f6b8e4f0..795e16d5d2f7 100644
> --- a/kernel/trace/bpf_trace.c
> +++ b/kernel/trace/bpf_trace.c
> @@ -2362,6 +2362,9 @@ int bpf_get_perf_event_info(const struct perf_event *event, u32 *prog_id,
> return -EOPNOTSUPP;
>
> *prog_id = prog->aux->id;
> + *probe_offset = 0x0;
> + *probe_addr = 0x0;
> +
> flags = event->tp_event->flags;
> is_tracepoint = flags & TRACE_EVENT_FL_TRACEPOINT;
> is_syscall_tp = is_syscall_trace_event(event->tp_event);
> @@ -2370,8 +2373,6 @@ int bpf_get_perf_event_info(const struct perf_event *event, u32 *prog_id,
> *buf = is_tracepoint ? event->tp_event->tp->name
> : event->tp_event->name;
> *fd_type = BPF_FD_TYPE_TRACEPOINT;
> - *probe_offset = 0x0;
> - *probe_addr = 0x0;
> } else {
> /* kprobe/uprobe */
> err = -EOPNOTSUPP;
--
Regards
Yafang
next prev parent reply other threads:[~2023-07-05 10:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 11:53 [PATCH v6 bpf-next 00/11] bpf: Support ->fill_link_info for kprobe_multi and perf_event links Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 01/11] bpf: Support ->fill_link_info for kprobe_multi Yafang Shao
2023-07-06 22:00 ` Andrii Nakryiko
2023-07-07 1:52 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 02/11] bpftool: Dump the kernel symbol's module name Yafang Shao
2023-06-29 13:46 ` Quentin Monnet
2023-06-30 2:22 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 03/11] bpftool: Show kprobe_multi link info Yafang Shao
2023-07-05 8:09 ` Daniel Borkmann
2023-07-05 9:59 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 04/11] bpf: Protect probed address based on kptr_restrict setting Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 05/11] bpf: Clear the probe_addr for uprobe Yafang Shao
2023-07-05 8:19 ` Daniel Borkmann
2023-07-05 10:00 ` Yafang Shao [this message]
2023-07-05 14:33 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 06/11] bpf: Expose symbol's respective address Yafang Shao
2023-07-05 8:26 ` Daniel Borkmann
2023-07-05 10:01 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 07/11] bpf: Add a common helper bpf_copy_to_user() Yafang Shao
2023-07-06 22:00 ` Andrii Nakryiko
2023-06-28 11:53 ` [PATCH v6 bpf-next 08/11] bpf: Add bpf_perf_link_fill_common() Yafang Shao
2023-07-06 22:00 ` Andrii Nakryiko
2023-07-07 1:49 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 09/11] bpf: Support ->fill_link_info for perf_event Yafang Shao
2023-07-05 8:46 ` Daniel Borkmann
2023-07-05 10:08 ` Yafang Shao
2023-07-05 12:30 ` Daniel Borkmann
2023-06-28 11:53 ` [PATCH v6 bpf-next 10/11] bpftool: Add perf event names Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 11/11] bpftool: Show perf link info Yafang Shao
2023-06-29 13:40 ` Quentin Monnet
2023-07-05 8:54 ` Daniel Borkmann
2023-07-05 10:13 ` Yafang Shao
2023-06-29 13:29 ` [PATCH v6 bpf-next 00/11] bpf: Support ->fill_link_info for kprobe_multi and perf_event links 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=CALOAHbDs1L4Pot4-M0g4b9uSCwZgQYb1SQZ-QqAdxvZGLdW0uw@mail.gmail.com \
--to=laoar.shao@gmail.com \
--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=kpsingh@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mhiramat@kernel.org \
--cc=quentin@isovalent.com \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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).