From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"selinux@vger.kernel.org" <selinux@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>
Subject: [PATCH v3 0/3] perf: make Perf tool aware of SELinux access control
Date: Thu, 30 Apr 2020 10:06:09 +0300 [thread overview]
Message-ID: <0fffd9e2-1f22-a0c2-c2e3-cb7f4bb89d66@linux.intel.com> (raw)
Changes in v3:
- mention "CAP_PERFMON or CAP_SYS_ADMIN" instead of sole CAP_PERFMON or
CAP_SYS_ADMIN capability in the docs and messages to support use case
of newer Perf tool on kernel w/o CAP_PERFMON
- reverted double new line in "No permission to enable %s event.\n\n"
- updated security.txt content with new messages wording
v2: https://lore.kernel.org/lkml/66f2975b-4a69-b428-7dc5-d9aa40b3c673@linux.intel.com/
Changes in v2:
- implemented minor doc and code changes to substitute CAP_SYS_ADMIN
with CAP_PERFMON capability;
- introduced Perf doc file with instructions on how to enable and use
perf_event LSM hooks for mandatory access control to perf_event_open()
syscall;
v1: https://lore.kernel.org/lkml/b8a0669e-36e4-a0e8-fd35-3dbd890d2170@linux.intel.com/
repo: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/core
sha1: ee097e8ee56f8867cbbf45fe2a06f6b9e660c39c
Extend Perf tool with the check of /sys/fs/selinux/enforce value and notify
in case access to perf_event_open() syscall is restricted by the enforced
SELinux policy settings. See new added security.txt file for exact steps
how the changes look like and how to test the patch set.
---
Alexey Budankov (3):
perf docs: extend CAP_SYS_ADMIN with CAP_PERFMON where needed
perf tool: make Perf tool aware of SELinux access control
perf docs: introduce security.txt file to document related issues
tools/perf/Documentation/perf-intel-pt.txt | 2 +-
tools/perf/Documentation/security.txt | 237 +++++++++++++++++++++
tools/perf/util/cloexec.c | 4 +-
tools/perf/util/evsel.c | 39 ++--
4 files changed, 264 insertions(+), 18 deletions(-)
create mode 100644 tools/perf/Documentation/security.txt
--
2.24.1
next reply other threads:[~2020-04-30 7:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 7:06 Alexey Budankov [this message]
2020-04-30 7:15 ` [PATCH v3 1/3] perf docs: extend CAP_SYS_ADMIN with CAP_PERFMON where needed Alexey Budankov
2020-04-30 7:15 ` [PATCH v3 2/3] perf tool: make Perf tool aware of SELinux access control Alexey Budankov
2020-05-18 15:58 ` Arnaldo Carvalho de Melo
2020-05-18 16:43 ` Alexey Budankov
2020-05-19 7:34 ` Alexey Budankov
2020-05-19 18:10 ` Arnaldo Carvalho de Melo
2020-04-30 7:16 ` [PATCH v3 3/3] perf docs: introduce security.txt file to document related issues Alexey Budankov
2020-05-18 15:59 ` Arnaldo Carvalho de Melo
2020-05-18 16:50 ` Alexey Budankov
2020-05-18 17:06 ` Arnaldo Carvalho de Melo
2020-05-18 8:07 ` [PATCH v3 0/3] perf: make Perf tool aware of SELinux access control Alexey Budankov
-- strict thread matches above, loose matches on Subject: below --
2020-04-24 6:45 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=0fffd9e2-1f22-a0c2-c2e3-cb7f4bb89d66@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=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=selinux@vger.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 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).