From: Peter Zijlstra <peterz@infradead.org>
To: Marco Elver <elver@google.com>
Cc: tglx@linutronix.de, mingo@kernel.org, dvyukov@google.com,
glider@google.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org,
linux-perf-users@vger.kernel.org, ebiederm@xmission.com,
omosnace@redhat.com, serge@hallyn.com,
linux-security-module@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] perf: Fix required permissions if sigtrap is requested
Date: Tue, 13 Jul 2021 11:48:25 +0200 [thread overview]
Message-ID: <20210713094825.GC4132@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CANpmjNP7Z0mxaF+eYCtP1aabPcoh-0aDSOiW6FQsPkR8SbVwnA@mail.gmail.com>
On Mon, Jul 12, 2021 at 12:32:33PM +0200, Marco Elver wrote:
> It'd be good to get this sorted -- please take another look.
Thanks!
I'll queue them into perf/urgent.
next prev parent reply other threads:[~2021-07-13 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 8:44 [PATCH v3 1/2] perf: Fix required permissions if sigtrap is requested Marco Elver
2021-07-05 8:44 ` [PATCH v3 2/2] perf: Refactor permissions check into perf_check_permission() Marco Elver
2021-07-06 6:16 ` Dmitry Vyukov
2021-07-27 13:58 ` [tip: perf/urgent] " tip-bot2 for Marco Elver
2021-07-06 6:16 ` [PATCH v3 1/2] perf: Fix required permissions if sigtrap is requested Dmitry Vyukov
2021-07-12 10:32 ` Marco Elver
2021-07-13 9:48 ` Peter Zijlstra [this message]
2021-07-27 13:58 ` [tip: perf/urgent] " tip-bot2 for Marco Elver
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=20210713094825.GC4132@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=jolsa@redhat.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=omosnace@redhat.com \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.