From: Mike Rapoport <rppt@kernel.org>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: David Hildenbrand <david@redhat.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Peter Xu <peterx@redhat.com>, Linux-MM <linux-mm@kvack.org>
Subject: Re: userfaultfd: usability issue due to lack of UFFD events ordering
Date: Tue, 1 Feb 2022 11:10:24 +0200 [thread overview]
Message-ID: <Yfj5AApMfWVateAr@kernel.org> (raw)
In-Reply-To: <B2B2DFF0-7967-4F80-8AAC-3DB0B3911CED@gmail.com>
On Mon, Jan 31, 2022 at 02:39:01PM -0800, Nadav Amit wrote:
> > On Jan 31, 2022, at 10:47 AM, Mike Rapoport <rppt@kernel.org> wrote:
> >
> > On Mon, Jan 31, 2022 at 03:41:05PM +0100, David Hildenbrand wrote:
>
> As for me, I decided that due to the lack of ordering, I just
> cannot use the UFFD events, and I have to rely on ptrace to obtain
> order of these events. I might be wrong, but any solution is not
> trivial and is likely to require API changes.
I think you are right and any solution that will allow userspace to track
the order of all events (page faults and address space changes) will
require API changes.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2022-02-01 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 6:23 userfaultfd: usability issue due to lack of UFFD events ordering Nadav Amit
2022-01-31 10:42 ` Mike Rapoport
2022-01-31 10:48 ` David Hildenbrand
2022-01-31 14:05 ` Mike Rapoport
2022-01-31 14:12 ` David Hildenbrand
2022-01-31 14:28 ` Mike Rapoport
2022-01-31 14:41 ` David Hildenbrand
2022-01-31 18:47 ` Mike Rapoport
2022-01-31 22:39 ` Nadav Amit
2022-02-01 9:10 ` Mike Rapoport [this message]
2022-02-10 7:48 ` Peter Xu
2022-02-10 18:42 ` Nadav Amit
2022-02-14 4:02 ` Peter Xu
2022-02-15 22:35 ` Nadav Amit
2022-02-16 8:27 ` Peter Xu
2022-02-17 21:15 ` Mike Rapoport
2022-01-31 17:23 ` Nadav Amit
2022-01-31 17:28 ` David Hildenbrand
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=Yfj5AApMfWVateAr@kernel.org \
--to=rppt@kernel.org \
--cc=aarcange@redhat.com \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.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;
as well as URLs for NNTP newsgroup(s).