From: "tip-bot2 for Alexey Budankov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Alexey Budankov <alexey.budankov@linux.intel.com>,
Alexei Starovoitov <ast@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Igor Lubashev <ilubashe@akamai.com>,
James Morris <jmorris@namei.org>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Serge Hallyn <serge@hallyn.com>, Song Liu <songliubraving@fb.com>,
Stephane Eranian <eranian@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
intel-gfx@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-man@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [tip: perf/core] doc/admin-guide: update kernel.rst with CAP_PERFMON information
Date: Wed, 22 Apr 2020 12:17:31 -0000 [thread overview]
Message-ID: <158755785160.28353.3846364615857444421.tip-bot2@tip-bot2> (raw)
In-Reply-To: <84c32383-14a2-fa35-16b6-f9e59bd37240@linux.intel.com>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 025b16f81dd7f51f29d0109399d669438c63b6ce
Gitweb: https://git.kernel.org/tip/025b16f81dd7f51f29d0109399d669438c63b6ce
Author: Alexey Budankov <alexey.budankov@linux.intel.com>
AuthorDate: Thu, 02 Apr 2020 11:54:39 +03:00
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitterDate: Thu, 16 Apr 2020 12:19:12 -03:00
doc/admin-guide: update kernel.rst with CAP_PERFMON information
Update the kernel.rst documentation file with the information related to
usage of CAP_PERFMON capability to secure performance monitoring and
observability operations in system.
Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Igor Lubashev <ilubashe@akamai.com>
Cc: James Morris <jmorris@namei.org>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Serge Hallyn <serge@hallyn.com>
Cc: Song Liu <songliubraving@fb.com>
Cc: Stephane Eranian <eranian@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: intel-gfx@lists.freedesktop.org
Cc: linux-doc@vger.kernel.org
Cc: linux-man@vger.kernel.org
Cc: linux-security-module@vger.kernel.org
Cc: selinux@vger.kernel.org
Link: http://lore.kernel.org/lkml/84c32383-14a2-fa35-16b6-f9e59bd37240@linux.intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
Documentation/admin-guide/sysctl/kernel.rst | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index 39c95c0..7e4c28d 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -730,7 +730,13 @@ perf_event_paranoid
===================
Controls use of the performance events system by unprivileged
-users (without CAP_SYS_ADMIN). The default value is 2.
+users (without CAP_PERFMON). The default value is 2.
+
+For backward compatibility reasons access to system performance
+monitoring and observability remains open for CAP_SYS_ADMIN
+privileged processes but CAP_SYS_ADMIN usage for secure system
+performance monitoring and observability operations is discouraged
+with respect to CAP_PERFMON use cases.
=== ==================================================================
-1 Allow use of (almost) all events by all users.
@@ -739,13 +745,13 @@ users (without CAP_SYS_ADMIN). The default value is 2.
``CAP_IPC_LOCK``.
>=0 Disallow ftrace function tracepoint by users without
- ``CAP_SYS_ADMIN``.
+ ``CAP_PERFMON``.
- Disallow raw tracepoint access by users without ``CAP_SYS_ADMIN``.
+ Disallow raw tracepoint access by users without ``CAP_PERFMON``.
->=1 Disallow CPU event access by users without ``CAP_SYS_ADMIN``.
+>=1 Disallow CPU event access by users without ``CAP_PERFMON``.
->=2 Disallow kernel profiling by users without ``CAP_SYS_ADMIN``.
+>=2 Disallow kernel profiling by users without ``CAP_PERFMON``.
=== ==================================================================
WARNING: multiple messages have this Message-ID (diff)
From: "tip-bot2 for Alexey Budankov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: linux-man@vger.kernel.org, Song Liu <songliubraving@fb.com>,
Andi Kleen <ak@linux.intel.com>,
linux-doc@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Igor Lubashev <ilubashe@akamai.com>,
Alexei Starovoitov <ast@kernel.org>,
Stephane Eranian <eranian@google.com>,
James Morris <jmorris@namei.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@redhat.com>,
intel-gfx@lists.freedesktop.org, x86 <x86@kernel.org>,
Serge Hallyn <serge@hallyn.com>
Subject: [Intel-gfx] [tip: perf/core] doc/admin-guide: update kernel.rst with CAP_PERFMON information
Date: Wed, 22 Apr 2020 12:17:31 -0000 [thread overview]
Message-ID: <158755785160.28353.3846364615857444421.tip-bot2@tip-bot2> (raw)
In-Reply-To: <84c32383-14a2-fa35-16b6-f9e59bd37240@linux.intel.com>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 025b16f81dd7f51f29d0109399d669438c63b6ce
Gitweb: https://git.kernel.org/tip/025b16f81dd7f51f29d0109399d669438c63b6ce
Author: Alexey Budankov <alexey.budankov@linux.intel.com>
AuthorDate: Thu, 02 Apr 2020 11:54:39 +03:00
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitterDate: Thu, 16 Apr 2020 12:19:12 -03:00
doc/admin-guide: update kernel.rst with CAP_PERFMON information
Update the kernel.rst documentation file with the information related to
usage of CAP_PERFMON capability to secure performance monitoring and
observability operations in system.
Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Igor Lubashev <ilubashe@akamai.com>
Cc: James Morris <jmorris@namei.org>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Serge Hallyn <serge@hallyn.com>
Cc: Song Liu <songliubraving@fb.com>
Cc: Stephane Eranian <eranian@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: intel-gfx@lists.freedesktop.org
Cc: linux-doc@vger.kernel.org
Cc: linux-man@vger.kernel.org
Cc: linux-security-module@vger.kernel.org
Cc: selinux@vger.kernel.org
Link: http://lore.kernel.org/lkml/84c32383-14a2-fa35-16b6-f9e59bd37240@linux.intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
Documentation/admin-guide/sysctl/kernel.rst | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index 39c95c0..7e4c28d 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -730,7 +730,13 @@ perf_event_paranoid
===================
Controls use of the performance events system by unprivileged
-users (without CAP_SYS_ADMIN). The default value is 2.
+users (without CAP_PERFMON). The default value is 2.
+
+For backward compatibility reasons access to system performance
+monitoring and observability remains open for CAP_SYS_ADMIN
+privileged processes but CAP_SYS_ADMIN usage for secure system
+performance monitoring and observability operations is discouraged
+with respect to CAP_PERFMON use cases.
=== ==================================================================
-1 Allow use of (almost) all events by all users.
@@ -739,13 +745,13 @@ users (without CAP_SYS_ADMIN). The default value is 2.
``CAP_IPC_LOCK``.
>=0 Disallow ftrace function tracepoint by users without
- ``CAP_SYS_ADMIN``.
+ ``CAP_PERFMON``.
- Disallow raw tracepoint access by users without ``CAP_SYS_ADMIN``.
+ Disallow raw tracepoint access by users without ``CAP_PERFMON``.
->=1 Disallow CPU event access by users without ``CAP_SYS_ADMIN``.
+>=1 Disallow CPU event access by users without ``CAP_PERFMON``.
->=2 Disallow kernel profiling by users without ``CAP_SYS_ADMIN``.
+>=2 Disallow kernel profiling by users without ``CAP_PERFMON``.
=== ==================================================================
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-22 12:19 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 8:42 [PATCH v8 00/12] Introduce CAP_PERFMON to secure system performance monitoring and observability Alexey Budankov
2020-04-02 8:42 ` [Intel-gfx] " Alexey Budankov
2020-04-02 8:45 ` [PATCH v8 01/12] capabilities: introduce CAP_PERFMON to kernel and user space Alexey Budankov
2020-04-02 8:45 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] capabilities: Introduce " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:46 ` [PATCH v8 02/12] perf/core: open access to the core for CAP_PERFMON privileged process Alexey Budankov
2020-04-02 8:46 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] perf/core: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:47 ` [PATCH v8 03/12] perf/core: open access to probes " Alexey Budankov
2020-04-02 8:47 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:47 ` [PATCH v8 04/12] perf tool: extend Perf tool with CAP_PERFMON capability support Alexey Budankov
2020-04-02 8:47 ` [Intel-gfx] " Alexey Budankov
2020-04-03 11:08 ` Jiri Olsa
2020-04-03 11:08 ` [Intel-gfx] " Jiri Olsa
2020-04-03 13:08 ` Alexey Budankov
2020-04-03 13:08 ` [Intel-gfx] " Alexey Budankov
2020-04-04 2:18 ` Namhyung Kim
2020-04-04 2:18 ` [Intel-gfx] " Namhyung Kim
2020-04-04 8:18 ` Alexey Budankov
2020-04-04 8:18 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] perf tools: Support CAP_PERFMON capability tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:48 ` [PATCH v8 05/12] drm/i915/perf: open access for CAP_PERFMON privileged process Alexey Budankov
2020-04-02 8:48 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] drm/i915/perf: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:48 ` [PATCH v8 06/12] trace/bpf_trace: open " Alexey Budankov
2020-04-02 8:48 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] trace/bpf_trace: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:49 ` [PATCH v8 07/12] powerpc/perf: open " Alexey Budankov
2020-04-02 8:49 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:50 ` [PATCH v8 08/12] parisc/perf: " Alexey Budankov
2020-04-02 8:50 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:51 ` [PATCH v8 09/12] drivers/perf: " Alexey Budankov
2020-04-02 8:51 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] drivers/perf: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:53 ` [PATCH v8 10/12] drivers/oprofile: open " Alexey Budankov
2020-04-02 8:53 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] drivers/oprofile: Open " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:54 ` [PATCH v8 11/12] doc/admin-guide: update perf-security.rst with CAP_PERFMON information Alexey Budankov
2020-04-02 8:54 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` [tip: perf/core] doc/admin-guide: Update " tip-bot2 for Alexey Budankov
2020-04-22 12:17 ` [Intel-gfx] " tip-bot2 for Alexey Budankov
2020-04-02 8:54 ` [PATCH v8 12/12] doc/admin-guide: update kernel.rst " Alexey Budankov
2020-04-02 8:54 ` [Intel-gfx] " Alexey Budankov
2020-04-05 14:10 ` Arnaldo Carvalho de Melo
2020-04-05 14:10 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-05 14:41 ` Alexey Budankov
2020-04-05 14:41 ` [Intel-gfx] " Alexey Budankov
2020-04-05 14:54 ` Alexey Budankov
2020-04-05 14:54 ` [Intel-gfx] " Alexey Budankov
2020-04-05 15:05 ` Arnaldo Carvalho de Melo
2020-04-05 15:05 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-05 15:51 ` Alexey Budankov
2020-04-05 15:51 ` [Intel-gfx] " Alexey Budankov
2020-04-22 12:17 ` tip-bot2 for Alexey Budankov [this message]
2020-04-22 12:17 ` [Intel-gfx] [tip: perf/core] " tip-bot2 for Alexey Budankov
2020-04-02 9:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev5) Patchwork
2020-04-02 10:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-04-03 11:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-04-05 16:00 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev6) Patchwork
2020-04-07 14:30 ` [PATCH v8 00/12] Introduce CAP_PERFMON to secure system performance monitoring and observability Arnaldo Carvalho de Melo
2020-04-07 14:30 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 14:35 ` Arnaldo Carvalho de Melo
2020-04-07 14:35 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 14:54 ` Alexey Budankov
2020-04-07 14:54 ` [Intel-gfx] " Alexey Budankov
2020-04-07 16:36 ` Arnaldo Carvalho de Melo
2020-04-07 16:36 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 16:40 ` Arnaldo Carvalho de Melo
2020-04-07 16:40 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 17:17 ` Alexey Budankov
2020-04-07 17:17 ` [Intel-gfx] " Alexey Budankov
2020-04-07 16:52 ` Alexey Budankov
2020-04-07 16:52 ` [Intel-gfx] " Alexey Budankov
2020-04-07 17:02 ` Arnaldo Carvalho de Melo
2020-04-07 17:02 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 17:32 ` Alexey Budankov
2020-04-07 17:32 ` [Intel-gfx] " Alexey Budankov
2020-04-07 16:56 ` Arnaldo Carvalho de Melo
2020-04-07 16:56 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-07 17:23 ` Arnaldo Carvalho de Melo
2020-04-07 17:23 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-04-22 19:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev18) Patchwork
2020-04-22 19:43 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-07-10 13:31 ` [PATCH v8 00/12] Introduce CAP_PERFMON to secure system performance monitoring and observability Ravi Bangoria
2020-07-10 13:31 ` [Intel-gfx] " Ravi Bangoria
2020-07-10 14:30 ` Alexey Budankov
2020-07-10 14:30 ` [Intel-gfx] " Alexey Budankov
2020-07-10 17:09 ` Arnaldo Carvalho de Melo
2020-07-10 17:09 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-07-13 9:48 ` Alexey Budankov
2020-07-13 9:48 ` [Intel-gfx] " Alexey Budankov
2020-07-13 12:17 ` Arnaldo Carvalho de Melo
2020-07-13 12:17 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-07-13 12:37 ` Alexey Budankov
2020-07-13 12:37 ` [Intel-gfx] " Alexey Budankov
2020-07-13 18:51 ` Arnaldo Carvalho de Melo
2020-07-13 18:51 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-07-14 10:59 ` Peter Zijlstra
2020-07-14 10:59 ` [Intel-gfx] " Peter Zijlstra
2020-07-14 15:27 ` Arnaldo Carvalho de Melo
2020-07-14 15:27 ` [Intel-gfx] " Arnaldo Carvalho de Melo
2020-07-21 13:06 ` Alexey Budankov
2020-07-21 13:06 ` [Intel-gfx] " Alexey Budankov
2020-07-22 11:30 ` Arnaldo Carvalho de Melo
2020-07-22 11:30 ` [Intel-gfx] " Arnaldo Carvalho de Melo
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=158755785160.28353.3846364615857444421.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=ast@kernel.org \
--cc=eranian@google.com \
--cc=ilubashe@akamai.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jmorris@namei.org \
--cc=jolsa@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.