From: David Hildenbrand <david@redhat.com>
To: Nadav Amit <nadav.amit@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Nadav Amit <namit@vmware.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: [RFC PATCH] userfaultfd: support control over mm of remote PIDs
Date: Mon, 27 Sep 2021 11:29:59 +0200 [thread overview]
Message-ID: <83827672-0996-4c25-9991-697ad443b6b3@redhat.com> (raw)
In-Reply-To: <20210926170637.245699-1-namit@vmware.com>
On 26.09.21 19:06, Nadav Amit wrote:
> From: Nadav Amit <namit@vmware.com>
>
> Non-cooperative mode is useful but only for forked processes.
> Userfaultfd can be useful to monitor, debug and manage memory of remote
> processes.
>
> To support this mode, add a new flag, UFFD_REMOTE_PID, and an optional
> second argument to the userfaultfd syscall. When the flag is set, the
> second argument is assumed to be the PID of the process that is to be
> monitored. Otherwise the flag is ignored.
>
> The syscall enforces that the caller has CAP_SYS_PTRACE to prevent
> misuse of this feature.
What supposed to happen if the target process intents to use uffd itself?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-09-27 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 17:06 Nadav Amit
2021-09-27 9:29 ` David Hildenbrand [this message]
2021-09-27 10:19 ` Nadav Amit
2021-09-27 17:06 ` David Hildenbrand
2021-09-27 20:08 ` Nadav Amit
2021-09-27 20:11 ` David Hildenbrand
2021-10-13 2:18 ` Peter Xu
2021-10-13 16:02 ` Nadav Amit
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=83827672-0996-4c25-9991-697ad443b6b3@redhat.com \
--to=david@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=namit@vmware.com \
--cc=peterx@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
/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