From: Andrea Arcangeli <aarcange@redhat.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Hillf Danton <hillf.zj@alibaba-inc.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Pavel Emelyanov <xemul@virtuozzo.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] userfaultfd: mcopy_atomic: update cases returning -ENOENT
Date: Tue, 7 Feb 2017 21:06:54 +0100 [thread overview]
Message-ID: <20170207200654.GK25530@redhat.com> (raw)
In-Reply-To: <20170207150249.GA6709@rapoport-lnx>
On Tue, Feb 07, 2017 at 05:02:50PM +0200, Mike Rapoport wrote:
> Hello Andrew,
>
> The patch below is an incremental fixup for concerns Andrea raised at [1].
> Please let me know if you prefer me to update the original patch and
> resend.
>
> [1] http://www.spinics.net/lists/linux-mm/msg121267.html
>
> --
> Sincerely yours,
> Mike.
>
> From 8acff65ecee8ca4cc892d35b45125c34568d1c93 Mon Sep 17 00:00:00 2001
> From: Mike Rapoport <rppt@linux.vnet.ibm.com>
> Date: Tue, 7 Feb 2017 11:50:17 +0200
> Subject: [PATCH] userfaultfd: mcopy_atomic: update cases returning -ENOENT
>
> As Andrea commented in [1], if the VMA covering the address was unmapped,
> we may end up with a VMA a way above the faulting address. In this case we
> would like to return -ENOENT to allow uffd monitor detection of VMA
> removal.
>
> [1] http://www.spinics.net/lists/linux-mm/msg121267.html
>
> Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
Reviewed-by: Andrea Arcangeli <aarcange@redhat.com>
--
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>
prev parent reply other threads:[~2017-02-07 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 15:02 [PATCH] userfaultfd: mcopy_atomic: update cases returning -ENOENT Mike Rapoport
2017-02-07 20:06 ` Andrea Arcangeli [this message]
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=20170207200654.GK25530@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dgilbert@redhat.com \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).