From: Andrea Arcangeli <aarcange@redhat.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pavel Emelyanov <xemul@virtuozzo.com>,
linux-mm@kvack.org
Subject: Re: [PATCH for 4.11] userfaultfd: report actual registered features in fdinfo
Date: Mon, 3 Apr 2017 18:30:34 +0200 [thread overview]
Message-ID: <20170403163034.GD5107@redhat.com> (raw)
In-Reply-To: <20170403151024.GA14802@rapoport-lnx>
Hello Mike,
On Mon, Apr 03, 2017 at 06:10:24PM +0300, Mike Rapoport wrote:
> Actually, I've found these details in /proc useful when I was experimenting
> with checkpoint-restore of an application that uses userfaultfd. With
> interface in /proc/<pid>/ we know exactly which process use userfaultfd and
> can act appropriately.
You've to be somewhat serialized by other means though, because
"exactly" has a limit with fdinfo. For example by the time read()
returns, the uffd may have been closed already by the app (just the
uffd isn't ->release()d yet as the last fput has yet to run, the
fdinfo runs the last fput in such case). As long as you can cope with
this and you've a stable fdinfo it's ok.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-04-03 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 13:36 Mike Rapoport
2017-04-03 14:35 ` Andrea Arcangeli
2017-04-03 15:10 ` Mike Rapoport
2017-04-03 16:30 ` Andrea Arcangeli [this message]
2017-04-04 7:46 ` Mike Rapoport
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=20170403163034.GD5107@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=xemul@virtuozzo.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