From: Andrea Arcangeli <aarcange@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Jan Kara <jack@suse.cz>,
ross.zwisler@linux.intel.com, Michal Hocko <mhocko@suse.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: mm: fault in __do_fault
Date: Tue, 28 Feb 2017 16:55:49 +0100 [thread overview]
Message-ID: <20170228155549.GJ5816@redhat.com> (raw)
In-Reply-To: <20170228153220.GA30524@node.shutemov.name>
On Tue, Feb 28, 2017 at 06:32:20PM +0300, Kirill A. Shutemov wrote:
> Andrea, does it look okay for you?
>
> diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
> index 625b7285a37b..56f61f1a1dc1 100644
> --- a/fs/userfaultfd.c
> +++ b/fs/userfaultfd.c
> @@ -489,7 +489,7 @@ int handle_userfault(struct vm_fault *vmf, unsigned long reason)
> * in such case.
> */
> down_read(&mm->mmap_sem);
> - ret = 0;
> + ret = VM_FAULT_NOPAGE;
> }
> }
Yes, I did the same fix.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <aarcange@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Jan Kara <jack@suse.cz>,
ross.zwisler@linux.intel.com, Michal Hocko <mhocko@suse.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: mm: fault in __do_fault
Date: Tue, 28 Feb 2017 16:55:49 +0100 [thread overview]
Message-ID: <20170228155549.GJ5816@redhat.com> (raw)
In-Reply-To: <20170228153220.GA30524@node.shutemov.name>
On Tue, Feb 28, 2017 at 06:32:20PM +0300, Kirill A. Shutemov wrote:
> Andrea, does it look okay for you?
>
> diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
> index 625b7285a37b..56f61f1a1dc1 100644
> --- a/fs/userfaultfd.c
> +++ b/fs/userfaultfd.c
> @@ -489,7 +489,7 @@ int handle_userfault(struct vm_fault *vmf, unsigned long reason)
> * in such case.
> */
> down_read(&mm->mmap_sem);
> - ret = 0;
> + ret = VM_FAULT_NOPAGE;
> }
> }
Yes, I did the same fix.
next prev parent reply other threads:[~2017-02-28 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 14:04 mm: fault in __do_fault Dmitry Vyukov
2017-02-28 14:04 ` Dmitry Vyukov
2017-02-28 15:32 ` Kirill A. Shutemov
2017-02-28 15:32 ` Kirill A. Shutemov
2017-02-28 15:55 ` Andrea Arcangeli [this message]
2017-02-28 15:55 ` Andrea Arcangeli
2017-02-28 15:42 ` Andrea Arcangeli
2017-02-28 15:42 ` Andrea Arcangeli
2017-03-03 7:42 ` Dmitry Vyukov
2017-03-03 7:42 ` Dmitry Vyukov
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=20170228155549.GJ5816@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=ross.zwisler@linux.intel.com \
--cc=syzkaller@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.