All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@redhat.com>,
	Andi Kleen <ak@linux.intel.com>,
	Igor Lubashev <ilubashe@akamai.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	James Morris <jmorris@namei.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 04/10] perf tool: extend Perf tool with CAP_PERFMON capability support
Date: Wed, 1 Apr 2020 23:50:16 +0300	[thread overview]
Message-ID: <0c8daba0-bc3c-26bf-e463-b8629403beff@linux.intel.com> (raw)
In-Reply-To: <f6eee965-e35d-e4dd-d794-85b7e152c428@linux.intel.com>


Hi Arnaldo,

On 28.01.2020 9:09, Alexey Budankov wrote:
> 
> Extend error messages to mention CAP_PERFMON capability as an option
> to substitute CAP_SYS_ADMIN capability for secure system performance
> monitoring and observability operations. Make perf_event_paranoid_check()
> and __cmd_ftrace() to be aware of CAP_PERFMON capability.
> 
> CAP_PERFMON implements the principal of least privilege for performance
> monitoring and observability operations (POSIX IEEE 1003.1e 2.2.2.39 principle
> of least privilege: A security design principle that states that a process
> or program be granted only those privileges (e.g., capabilities) necessary
> to accomplish its legitimate function, and only for the time that such
> privileges are actually required)
> 
> For backward compatibility reasons access to perf_events subsystem remains
> open for CAP_SYS_ADMIN privileged processes but CAP_SYS_ADMIN usage for
> secure perf_events monitoring is discouraged with respect to CAP_PERFMON
> capability.
> 
> Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
> ---
>  tools/perf/builtin-ftrace.c |  5 +++--
>  tools/perf/design.txt       |  3 ++-
>  tools/perf/util/cap.h       |  4 ++++
>  tools/perf/util/evsel.c     | 10 +++++-----
>  tools/perf/util/util.c      |  1 +
>  5 files changed, 15 insertions(+), 8 deletions(-)

Could this have you explicit Reviewed-by or Acked-by tag
so the changes could be driven into the kernel?
Latest v7 is here:
https://lore.kernel.org/lkml/c8de937a-0b3a-7147-f5ef-69f467e87a13@linux.intel.com/

Thanks,
Alexey


> 
> diff --git a/tools/perf/builtin-ftrace.c b/tools/perf/builtin-ftrace.c
> index d5adc417a4ca..55eda54240fb 100644
> --- a/tools/perf/builtin-ftrace.c
> +++ b/tools/perf/builtin-ftrace.c
> @@ -284,10 +284,11 @@ static int __cmd_ftrace(struct perf_ftrace *ftrace, int argc, const char **argv)
>  		.events = POLLIN,
>  	};
>  
> -	if (!perf_cap__capable(CAP_SYS_ADMIN)) {
> +	if (!(perf_cap__capable(CAP_PERFMON) ||
> +	      perf_cap__capable(CAP_SYS_ADMIN))) {
>  		pr_err("ftrace only works for %s!\n",
>  #ifdef HAVE_LIBCAP_SUPPORT
> -		"users with the SYS_ADMIN capability"
> +		"users with the CAP_PERFMON or CAP_SYS_ADMIN capability"
>  #else
>  		"root"
>  #endif
> diff --git a/tools/perf/design.txt b/tools/perf/design.txt
> index 0453ba26cdbd..a42fab308ff6 100644
> --- a/tools/perf/design.txt
> +++ b/tools/perf/design.txt
> @@ -258,7 +258,8 @@ gets schedule to. Per task counters can be created by any user, for
>  their own tasks.
>  
>  A 'pid == -1' and 'cpu == x' counter is a per CPU counter that counts
> -all events on CPU-x. Per CPU counters need CAP_SYS_ADMIN privilege.
> +all events on CPU-x. Per CPU counters need CAP_PERFMON or CAP_SYS_ADMIN
> +privilege.
>  
>  The 'flags' parameter is currently unused and must be zero.
>  
> diff --git a/tools/perf/util/cap.h b/tools/perf/util/cap.h
> index 051dc590ceee..ae52878c0b2e 100644
> --- a/tools/perf/util/cap.h
> +++ b/tools/perf/util/cap.h
> @@ -29,4 +29,8 @@ static inline bool perf_cap__capable(int cap __maybe_unused)
>  #define CAP_SYSLOG	34
>  #endif
>  
> +#ifndef CAP_PERFMON
> +#define CAP_PERFMON	38
> +#endif
> +
>  #endif /* __PERF_CAP_H */
> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> index a69e64236120..a35f17723dd3 100644
> --- a/tools/perf/util/evsel.c
> +++ b/tools/perf/util/evsel.c
> @@ -2491,14 +2491,14 @@ int perf_evsel__open_strerror(struct evsel *evsel, struct target *target,
>  		 "You may not have permission to collect %sstats.\n\n"
>  		 "Consider tweaking /proc/sys/kernel/perf_event_paranoid,\n"
>  		 "which controls use of the performance events system by\n"
> -		 "unprivileged users (without CAP_SYS_ADMIN).\n\n"
> +		 "unprivileged users (without CAP_PERFMON or CAP_SYS_ADMIN).\n\n"
>  		 "The current value is %d:\n\n"
>  		 "  -1: Allow use of (almost) all events by all users\n"
>  		 "      Ignore mlock limit after perf_event_mlock_kb without CAP_IPC_LOCK\n"
> -		 ">= 0: Disallow ftrace function tracepoint by users without CAP_SYS_ADMIN\n"
> -		 "      Disallow raw tracepoint access by users without CAP_SYS_ADMIN\n"
> -		 ">= 1: Disallow CPU event access by users without CAP_SYS_ADMIN\n"
> -		 ">= 2: Disallow kernel profiling by users without CAP_SYS_ADMIN\n\n"
> +		 ">= 0: Disallow ftrace function tracepoint by users without CAP_PERFMON or CAP_SYS_ADMIN\n"
> +		 "      Disallow raw tracepoint access by users without CAP_SYS_PERFMON or CAP_SYS_ADMIN\n"
> +		 ">= 1: Disallow CPU event access by users without CAP_PERFMON or CAP_SYS_ADMIN\n"
> +		 ">= 2: Disallow kernel profiling by users without CAP_PERFMON or CAP_SYS_ADMIN\n\n"
>  		 "To make this setting permanent, edit /etc/sysctl.conf too, e.g.:\n\n"
>  		 "	kernel.perf_event_paranoid = -1\n" ,
>  				 target->system_wide ? "system-wide " : "",
> diff --git a/tools/perf/util/util.c b/tools/perf/util/util.c
> index 969ae560dad9..51cf3071db74 100644
> --- a/tools/perf/util/util.c
> +++ b/tools/perf/util/util.c
> @@ -272,6 +272,7 @@ int perf_event_paranoid(void)
>  bool perf_event_paranoid_check(int max_level)
>  {
>  	return perf_cap__capable(CAP_SYS_ADMIN) ||
> +			perf_cap__capable(CAP_PERFMON) ||
>  			perf_event_paranoid() <= max_level;
>  }
>  
> 

  reply	other threads:[~2020-04-01 20:50 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  5:52 [PATCH v6 00/10] Introduce CAP_PERFMON to secure system performance monitoring and observability Alexey Budankov
2020-01-28  5:52 ` [Intel-gfx] " Alexey Budankov
2020-01-28  5:52 ` Alexey Budankov
2020-01-28  5:52 ` Alexey Budankov
2020-01-28  5:52 ` Alexey Budankov
2020-01-28  6:07 ` [PATCH v6 01/10] capabilities: introduce CAP_PERFMON to kernel and user space Alexey Budankov
2020-01-28  6:07   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:07   ` Alexey Budankov
2020-01-28  6:07   ` Alexey Budankov
2020-01-28  6:07   ` Alexey Budankov
2020-01-28 21:16   ` James Morris
2020-01-28 21:16     ` [Intel-gfx] " James Morris
2020-01-28 21:16     ` James Morris
2020-01-28 21:16     ` James Morris
2020-01-28 21:16     ` James Morris
2020-01-28  6:08 ` [PATCH v6 02/10] perf/core: open access to the core for CAP_PERFMON privileged process Alexey Budankov
2020-01-28  6:08   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:08   ` Alexey Budankov
2020-01-28  6:08   ` Alexey Budankov
2020-01-28  6:08   ` Alexey Budankov
2020-01-28  6:09 ` [PATCH v6 03/10] perf/core: open access to probes " Alexey Budankov
2020-01-28  6:09   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:09   ` Alexey Budankov
2020-01-28  6:09   ` Alexey Budankov
2020-01-28  6:09   ` Alexey Budankov
2020-01-28 21:16   ` James Morris
2020-01-28 21:16     ` [Intel-gfx] " James Morris
2020-01-28 21:16     ` James Morris
2020-01-28 21:16     ` James Morris
2020-01-28 21:16     ` James Morris
2020-01-28  6:09 ` [PATCH v6 04/10] perf tool: extend Perf tool with CAP_PERFMON capability support Alexey Budankov
2020-01-28  6:09   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:09   ` Alexey Budankov
2020-01-28  6:09   ` Alexey Budankov
2020-01-28  6:09   ` Alexey Budankov
2020-04-01 20:50   ` Alexey Budankov [this message]
2020-01-28  6:10 ` [PATCH v6 05/10] drm/i915/perf: open access for CAP_PERFMON privileged process Alexey Budankov
2020-01-28  6:10   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:10   ` Alexey Budankov
2020-01-28  6:10   ` Alexey Budankov
2020-01-28  6:10   ` Alexey Budankov
2020-01-28  6:11 ` [PATCH v6 06/10] trace/bpf_trace: " Alexey Budankov
2020-01-28  6:11   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:11   ` Alexey Budankov
2020-01-28  6:11   ` Alexey Budankov
2020-01-28  6:11   ` Alexey Budankov
2020-01-28 21:17   ` James Morris
2020-01-28 21:17     ` [Intel-gfx] " James Morris
2020-01-28 21:17     ` James Morris
2020-01-28 21:17     ` James Morris
2020-01-28 21:17     ` James Morris
2020-01-28  6:12 ` [PATCH v6 07/10] powerpc/perf: " Alexey Budankov
2020-01-28  6:12   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:12   ` Alexey Budankov
2020-01-28  6:12   ` Alexey Budankov
2020-01-28  6:12   ` Alexey Budankov
2020-01-28 21:17   ` James Morris
2020-01-28 21:17     ` [Intel-gfx] " James Morris
2020-01-28 21:17     ` James Morris
2020-01-28 21:17     ` James Morris
2020-01-28 21:17     ` James Morris
2020-01-28  6:12 ` [PATCH v6 08/10] parisc/perf: " Alexey Budankov
2020-01-28  6:12   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:12   ` Alexey Budankov
2020-01-28  6:12   ` Alexey Budankov
2020-01-28  6:12   ` Alexey Budankov
2020-01-28 21:17   ` James Morris
2020-01-28 21:17     ` [Intel-gfx] " James Morris
2020-01-28 21:17     ` James Morris
2020-01-28 21:17     ` James Morris
2020-01-28 21:17     ` James Morris
2020-01-28  6:13 ` [PATCH v6 09/10] drivers/perf: " Alexey Budankov
2020-01-28  6:13   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:13   ` Alexey Budankov
2020-01-28  6:13   ` Alexey Budankov
2020-01-28  6:13   ` Alexey Budankov
2020-01-28 21:18   ` James Morris
2020-01-28 21:18     ` [Intel-gfx] " James Morris
2020-01-28 21:18     ` James Morris
2020-01-28 21:18     ` James Morris
2020-01-28 21:18     ` James Morris
2020-01-28  6:14 ` [PATCH v6 10/10] drivers/oprofile: " Alexey Budankov
2020-01-28  6:14   ` [Intel-gfx] " Alexey Budankov
2020-01-28  6:14   ` Alexey Budankov
2020-01-28  6:14   ` Alexey Budankov
2020-01-28  6:14   ` Alexey Budankov
2020-01-28 21:18   ` James Morris
2020-01-28 21:18     ` [Intel-gfx] " James Morris
2020-01-28 21:18     ` James Morris
2020-01-28 21:18     ` James Morris
2020-01-28 21:18     ` James Morris
2020-01-28  6:42 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev2) Patchwork
2020-01-28  7:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-29  6:03 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-02-05 17:25 [PATCH v6 00/10] Introduce CAP_PERFMON to secure system performance monitoring and observability Alexey Budankov
2020-02-05 17:32 ` [PATCH v6 04/10] perf tool: extend Perf tool with CAP_PERFMON capability support Alexey Budankov
2020-02-05 17:32   ` Alexey Budankov
2020-02-05 17:32   ` Alexey Budankov

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=0c8daba0-bc3c-26bf-e463-b8629403beff@linux.intel.com \
    --to=alexey.budankov@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ilubashe@akamai.com \
    --cc=jmorris@namei.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.