From: Daniel Colascione <dancol@google.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jann Horn <jannh@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Lokesh Gidra <lokeshgidra@google.com>,
Nick Kralevich <nnk@google.com>, Nosh Minwalla <nosh@google.com>,
Pavel Emelyanov <ovzxemul@gmail.com>,
Tim Murray <timmurray@google.com>,
Linux API <linux-api@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 1/1] userfaultfd: require CAP_SYS_PTRACE for UFFD_FEATURE_EVENT_FORK
Date: Tue, 5 Nov 2019 08:41:18 -0800 [thread overview]
Message-ID: <CAKOZuet=g++G+biSP5bU-Rppu6fykU1TVUDj20NapqAYQY4r9A@mail.gmail.com> (raw)
In-Reply-To: <20191105162424.GH30717@redhat.com>
On Tue, Nov 5, 2019 at 8:24 AM Andrea Arcangeli <aarcange@redhat.com> wrote:
> The long term plan is to introduce UFFD_FEATURE_EVENT_FORK2 feature
> flag that uses the ioctl to receive the child uffd, it'll consume more
> CPU, but it wouldn't require the PTRACE privilege anymore.
Why not just have callers retrieve FDs using recvmsg? This way, you
retrieve the message packet and the file descriptor at the same time
and you don't need any appreciable extra CPU use.
next prev parent reply other threads:[~2019-11-05 16:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 15:29 [PATCH 0/1] " Mike Rapoport
2019-11-05 15:29 ` [PATCH 1/1] " Mike Rapoport
2019-11-05 15:37 ` Andrea Arcangeli
2019-11-05 15:55 ` Daniel Colascione
2019-11-05 16:00 ` Andy Lutomirski
2019-11-05 16:06 ` Daniel Colascione
2019-11-05 16:33 ` Andrea Arcangeli
2019-11-05 16:39 ` Daniel Colascione
2019-11-05 16:55 ` Andrea Arcangeli
2019-11-05 17:02 ` Daniel Colascione
2019-11-05 17:30 ` Andrea Arcangeli
2019-11-05 22:01 ` Andy Lutomirski
2019-11-05 22:10 ` Daniel Colascione
2019-11-05 16:24 ` Andrea Arcangeli
2019-11-05 16:41 ` Daniel Colascione [this message]
2019-11-07 8:39 ` Mike Rapoport
2019-11-07 8:54 ` Daniel Colascione
2019-11-07 15:38 ` Andrea Arcangeli
2019-11-07 16:15 ` Daniel Colascione
2019-11-07 18:22 ` Andrea Arcangeli
2019-11-07 18:50 ` Daniel Colascione
2019-11-07 19:27 ` Andrea Arcangeli
2019-11-10 17:02 ` Andy Lutomirski
2019-11-05 15:59 ` Aleksa Sarai
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='CAKOZuet=g++G+biSP5bU-Rppu6fykU1TVUDj20NapqAYQY4r9A@mail.gmail.com' \
--to=dancol@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=luto@kernel.org \
--cc=nnk@google.com \
--cc=nosh@google.com \
--cc=ovzxemul@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=timmurray@google.com \
--cc=torvalds@linux-foundation.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