[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190217161428.6b43608a@lwn.net>
Date: Sun, 17 Feb 2019 16:14:28 -0700
From: Jonathan Corbet <corbet@....net>
To: Alexey Budankov <alexey.budankov@...ux.intel.com>
Cc: Kees Cook <keescook@...omium.org>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>, Peter Zijlstra <peterz@...radead.org>, Jann
Horn <jannh@...gle.com>, Arnaldo Carvalho de Melo <acme@...nel.org>, Jiri
Olsa <jolsa@...hat.com>, Namhyung Kim <namhyung@...nel.org>, Alexander
Shishkin <alexander.shishkin@...ux.intel.com>, Andi Kleen
<ak@...ux.intel.com>, Mark Rutland <mark.rutland@....com>, Tvrtko Ursulin
<tvrtko.ursulin@...ux.intel.com>, "kernel-hardening@...ts.openwall.com"
<kernel-hardening@...ts.openwall.com>, "linux-doc@...r.kernel.org"
<linux-doc@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/3] admin-guide: extend perf-security with resource
control, data categories and privileged users
On Mon, 11 Feb 2019 16:32:33 +0300
Alexey Budankov <alexey.budankov@...ux.intel.com> wrote:
> The patch set extends the first version of perf-security.rst documentation
> file [1], [2], [3] with the following topics:
>
> 1) perf_events/Perf resource limits and control management that describes
> RLIMIT_NOFILE and perf_event_mlock_kb settings for processes conducting
> performance monitoring;
>
> 2) categories of system and performance data that can be captured by
> perf_events/Perf with explicit designation of process sensitive data;
>
> 3) possible steps to create perf_event/Perf privileged users groups for
> the current implementations of perf_events syscall API [4] and Perf tool;
I've applied the set, thanks.
jon
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
