From: Peter Xu <peterx@redhat.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Mike Rapoport <rppt@linux.ibm.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Hugh Dickins <hughd@google.com>,
Pavel Emelyanov <xemul@virtuozzo.com>,
Pravin Shedge <pravin.shedge4linux@gmail.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] userfaultfd: clear flag if remap event not enabled
Date: Tue, 11 Dec 2018 13:16:25 +0800 [thread overview]
Message-ID: <20181211051625.GB3260@xz-x1> (raw)
In-Reply-To: <20181210200925.GA14751@redhat.com>
On Mon, Dec 10, 2018 at 03:09:25PM -0500, Andrea Arcangeli wrote:
> Hello,
>
> On Mon, Dec 10, 2018 at 07:51:16PM +0200, Mike Rapoport wrote:
> > On Mon, Dec 10, 2018 at 02:51:21PM +0800, Peter Xu wrote:
> > > When the process being tracked do mremap() without
> > > UFFD_FEATURE_EVENT_REMAP on the corresponding tracking uffd file
> > > handle, we should not generate the remap event, and at the same
> > > time we should clear all the uffd flags on the new VMA. Without
> > > this patch, we can still have the VM_UFFD_MISSING|VM_UFFD_WP
> > > flags on the new VMA even the fault handling process does not
> > > even know the existance of the VMA.
> > >
> > > CC: Andrea Arcangeli <aarcange@redhat.com>
> > > CC: Andrew Morton <akpm@linux-foundation.org>
> > > CC: Mike Rapoport <rppt@linux.vnet.ibm.com>
> > > CC: Kirill A. Shutemov <kirill@shutemov.name>
> > > CC: Hugh Dickins <hughd@google.com>
> > > CC: Pavel Emelyanov <xemul@virtuozzo.com>
> > > CC: Pravin Shedge <pravin.shedge4linux@gmail.com>
> > > CC: linux-mm@kvack.org
> > > CC: linux-kernel@vger.kernel.org
> > > Signed-off-by: Peter Xu <peterx@redhat.com>
> > > ---
> > > fs/userfaultfd.c | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
> > > index cd58939dc977..798ae8a438ff 100644
> > > --- a/fs/userfaultfd.c
> > > +++ b/fs/userfaultfd.c
> > > @@ -740,6 +740,9 @@ void mremap_userfaultfd_prep(struct vm_area_struct *vma,
> > > vm_ctx->ctx = ctx;
> > > userfaultfd_ctx_get(ctx);
> > > WRITE_ONCE(ctx->mmap_changing, true);
> > > + } else if (ctx) {
> > > + vma->vm_userfaultfd_ctx = NULL_VM_UFFD_CTX;
> > > + vma->vm_flags &= ~(VM_UFFD_WP | VM_UFFD_MISSING);
>
> Great catch Peter!
>
> >
> > My preference would be
> >
> > if (!ctx)
> > return;
> >
> > if (ctx->features & UFFD_FEATURE_EVENT_REMAP) {
> > ...
> > } else {
> > ...
> > }
> >
> > but I don't feel strongly about it.
>
> Yes, it'd look nicer to run a single "ctx not null" check.
I agree.
>
> >
> > I'd appreciate a comment in the code and with it
> >
> > Acked-by: Mike Rapoport <rppt@linux.ibm.com>
> >
>
> Reviewed-by: Andrea Arcangeli <aarcange@redhat.com>
Thanks to both! I'll repost soon.
Regards,
--
Peter Xu
prev parent reply other threads:[~2018-12-11 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 6:51 Peter Xu
2018-12-10 17:51 ` Mike Rapoport
2018-12-10 20:09 ` Andrea Arcangeli
2018-12-11 5:16 ` Peter Xu [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=20181211051625.GB3260@xz-x1 \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pravin.shedge4linux@gmail.com \
--cc=rppt@linux.ibm.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