From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Igor Lubashev <ilubashe@akamai.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Alexey Budankov <alexey.budankov@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH v3 4/4] perf: Use CAP_SYS_ADMIN instead of euid==0 with ftrace
Date: Mon, 12 Aug 2019 17:29:47 -0300 [thread overview]
Message-ID: <20190812202947.GI9280@kernel.org> (raw)
In-Reply-To: <20190812202706.GH9280@kernel.org>
Em Mon, Aug 12, 2019 at 05:27:06PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Aug 12, 2019 at 05:22:51PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Wed, Aug 07, 2019 at 10:44:17AM -0400, Igor Lubashev escreveu:
> > > @@ -281,7 +283,7 @@ static int __cmd_ftrace(struct perf_ftrace *ftrace, int argc, const char **argv)
> > > .events = POLLIN,
> > > };
> > >
> > > - if (geteuid() != 0) {
> > > + if (!perf_cap__capable(CAP_SYS_ADMIN)) {
> > > pr_err("ftrace only works for root!\n");
> >
> > I guess we should update the error message too?
> >
>
> I.e. I applied this as a follow up patch:
>
> diff --git a/tools/perf/builtin-ftrace.c b/tools/perf/builtin-ftrace.c
> index 01a5bb58eb04..ba8b65c2f9dc 100644
> --- a/tools/perf/builtin-ftrace.c
> +++ b/tools/perf/builtin-ftrace.c
> @@ -284,7 +284,12 @@ static int __cmd_ftrace(struct perf_ftrace *ftrace, int argc, const char **argv)
> };
>
> if (!perf_cap__capable(CAP_SYS_ADMIN)) {
> - pr_err("ftrace only works for root!\n");
> + pr_err("ftrace only works for %s!\n",
> +#ifdef HAVE_LIBCAP_SUPPORT
> + "users with the SYS_ADMIN capability"
> +#else
> + "root"
> +#endif
);
:-)
> return -1;
> }
>
I've pushed the whole set to my tmp.perf/cap branch, please chec
- Arnaldo
next prev parent reply other threads:[~2019-08-12 20:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 14:44 [PATCH v3 0/4] perf: Use capabilities instead of uid and euid Igor Lubashev
2019-08-07 14:44 ` [PATCH v3 1/4] perf: Add capability-related utilities Igor Lubashev
2019-08-12 19:43 ` Arnaldo Carvalho de Melo
2019-08-15 9:24 ` [tip:perf/core] tools build: Add capability-related feature detection tip-bot for Igor Lubashev
2019-08-15 9:25 ` [tip:perf/core] perf tools: Add helpers to use capabilities if present tip-bot for Igor Lubashev
2019-08-07 14:44 ` [PATCH v3 2/4] perf: Use CAP_SYS_ADMIN with perf_event_paranoid checks Igor Lubashev
2019-08-12 20:01 ` Arnaldo Carvalho de Melo
2019-08-12 20:15 ` Arnaldo Carvalho de Melo
2019-08-12 22:33 ` Lubashev, Igor
2019-08-13 13:20 ` Arnaldo Carvalho de Melo
2019-08-07 14:44 ` [PATCH v3 3/4] perf: Use CAP_SYSLOG with kptr_restrict checks Igor Lubashev
2019-08-14 18:04 ` Mathieu Poirier
2019-08-14 18:48 ` Arnaldo Carvalho de Melo
2019-08-14 18:52 ` Arnaldo Carvalho de Melo
2019-08-14 20:02 ` Lubashev, Igor
2019-08-15 15:01 ` Mathieu Poirier
2019-08-15 20:16 ` Mathieu Poirier
2019-08-15 21:42 ` Arnaldo Carvalho de Melo
2019-08-19 16:51 ` Mathieu Poirier
2019-08-19 22:22 ` Lubashev, Igor
2019-08-20 16:57 ` Mathieu Poirier
2019-08-20 17:13 ` Arnaldo Carvalho de Melo
2019-08-27 1:58 ` Lubashev, Igor
2019-08-15 22:27 ` Lubashev, Igor
2019-08-07 14:44 ` [PATCH v3 4/4] perf: Use CAP_SYS_ADMIN instead of euid==0 with ftrace Igor Lubashev
2019-08-12 20:22 ` Arnaldo Carvalho de Melo
2019-08-12 20:27 ` Arnaldo Carvalho de Melo
2019-08-12 20:29 ` Arnaldo Carvalho de Melo [this message]
2019-08-12 21:42 ` Mathieu Poirier
2019-08-13 13:23 ` Arnaldo Carvalho de Melo
2019-08-13 16:35 ` Mathieu Poirier
2019-08-15 9:27 ` [tip:perf/core] perf ftrace: Use CAP_SYS_ADMIN instead of euid==0 tip-bot for Igor Lubashev
2019-08-12 9:13 ` [PATCH v3 0/4] perf: Use capabilities instead of uid and euid 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=20190812202947.GI9280@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=ilubashe@akamai.com \
--cc=jmorris@namei.org \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.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).