Messages in this thread | | | Subject | Re: [RFC PATCH] userfaultfd: support control over mm of remote PIDs | From | David Hildenbrand <> | Date | Mon, 27 Sep 2021 11:29:59 +0200 |
| |
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
| |