From: Kees Cook <keescook@chromium.org>
To: John Dias <joaodias@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Min Chong <mchong@google.com>
Subject: Re: [PATCH] perf: protect group_leader from races that cause ctx
Date: Mon, 9 Jan 2017 15:16:58 -0800 [thread overview]
Message-ID: <CAGXu5jKhgD=kKsC=hUM7uMBG8zzoD4UfTZ0YAkkcn+54TU+RSQ@mail.gmail.com> (raw)
In-Reply-To: <CA+njcd30PbC=V=rcWwNOGE1FKxfb5=Fq6_q++Pkh58HgZ98BnQ@mail.gmail.com>
On Sat, Jan 7, 2017 at 8:29 AM, John Dias <joaodias@google.com> wrote:
>> John, are you able to test this solution? IIUC, you've got a reproducer handy?
>
> Yes, I tested against two reproducers. Both were fixed by this solution.
Great! Thanks for testing this.
> Thanks to Kees and Peter for your patience on this.
Peter, can you push your patch into the tree with the adjusted
Reported-by and Cc: stable (and maybe add Tested-by from John)?
Thanks again for working on it!
-Kees
--
Kees Cook
Nexus Security
next prev parent reply other threads:[~2017-01-09 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 23:14 [PATCH] perf: protect group_leader from races that cause ctx Kees Cook
2017-01-06 9:32 ` Peter Zijlstra
2017-01-06 13:14 ` Peter Zijlstra
2017-01-06 20:39 ` Kees Cook
2017-01-07 16:29 ` John Dias
2017-01-09 23:16 ` Kees Cook [this message]
2017-01-10 8:46 ` Peter Zijlstra
2017-01-10 10:16 ` Ingo Molnar
2017-01-10 23:54 ` Kees Cook
2017-01-14 12:28 ` [tip:perf/urgent] perf/core: Fix concurrent sys_perf_event_open() vs. 'move_group' race tip-bot for Peter Zijlstra
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='CAGXu5jKhgD=kKsC=hUM7uMBG8zzoD4UfTZ0YAkkcn+54TU+RSQ@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=joaodias@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchong@google.com \
--cc=mingo@redhat.com \
--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 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).