From: Song Liu <songliubraving@fb.com>
To: lkml <linux-kernel@vger.kernel.org>, Kernel Team <Kernel-team@fb.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v2] perf: allow non-privileged uprobe for user processes
Date: Thu, 9 May 2019 13:47:21 +0000 [thread overview]
Message-ID: <00FF6475-45B9-49B6-B434-A5F7BD884A87@fb.com> (raw)
In-Reply-To: <20190507161545.788381-1-songliubraving@fb.com>
Hi Peter,
> On May 7, 2019, at 9:15 AM, Song Liu <songliubraving@fb.com> wrote:
>
> Currently, non-privileged user could only use uprobe with
>
> kernel.perf_event_paranoid = -1
>
> However, setting perf_event_paranoid to -1 leaks other users' processes to
> non-privileged uprobes.
>
> To introduce proper permission control of uprobes, we are building the
> following system:
> A daemon with CAP_SYS_ADMIN is in charge to create uprobes via tracefs;
> Users asks the daemon to create uprobes;
> Then user can attach uprobe only to processes owned by the user.
>
> This patch allows non-privileged user to attach uprobe to processes owned
> by the user.
>
> The following example shows how to use uprobe with non-privileged user.
> This is based on Brendan's blog post [1]
>
> 1. Create uprobe with root:
> sudo perf probe -x 'readline%return +0($retval):string'
>
> 2. Then non-root user can use the uprobe as:
> perf record -vvv -e probe_bash:readline__return -p <pid> sleep 20
> perf script
>
> [1] http://www.brendangregg.com/blog/2015-06-28/linux-ftrace-uprobe.html
>
> Signed-off-by: Song Liu <songliubraving@fb.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Jiri Olsa <jolsa@redhat.com>
> ---
> kernel/events/core.c | 4 ++--
> kernel/trace/trace_uprobe.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index abbd4b3b96c2..3005c80f621d 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -8532,9 +8532,9 @@ static int perf_tp_event_match(struct perf_event *event,
> if (event->hw.state & PERF_HES_STOPPED)
> return 0;
> /*
> - * All tracepoints are from kernel-space.
> + * If exclude_kernel, only trace user-space tracepoints (uprobes)
> */
> - if (event->attr.exclude_kernel)
> + if (event->attr.exclude_kernel && !user_mode(regs))
> return 0;
>
> if (!perf_tp_filter_match(event, data))
> diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
> index be78d99ee6bc..bfd3040b4cfb 100644
> --- a/kernel/trace/trace_uprobe.c
> +++ b/kernel/trace/trace_uprobe.c
> @@ -1304,7 +1304,7 @@ static inline void init_trace_event_call(struct trace_uprobe *tu,
> call->event.funcs = &uprobe_funcs;
> call->class->define_fields = uprobe_event_define_fields;
>
> - call->flags = TRACE_EVENT_FL_UPROBE;
> + call->flags = TRACE_EVENT_FL_UPROBE | TRACE_EVENT_FL_CAP_ANY;
> call->class->reg = trace_uprobe_register;
> call->data = tu;
> }
> --
> 2.17.1
>
Could you please share your feedback on this version?
Thanks,
Song
next prev parent reply other threads:[~2019-05-09 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:15 Song Liu
2019-05-09 13:47 ` Song Liu [this message]
2019-06-03 13:23 ` [tip:perf/core] perf/core: Allow " tip-bot for Song Liu
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=00FF6475-45B9-49B6-B434-A5F7BD884A87@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®