From: Wei Yang <richardw.yang@linux.intel.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Wei Yang <richardw.yang@linux.intel.com>,
akpm@linux-foundation.org, aarcange@redhat.com, hughd@google.com,
linux-mm@kvack.org
Subject: Re: [PATCH 1/2] userfaultfd: remove one unnecessary warn_on in __mcopy_atomic_hugetlb
Date: Thu, 26 Sep 2019 08:35:28 +0800 [thread overview]
Message-ID: <20190926003528.GA3162@richard> (raw)
In-Reply-To: <3f69dc19-eb3b-ed46-62bc-c5e6e89ab6eb@oracle.com>
On Wed, Sep 25, 2019 at 10:44:58AM -0700, Mike Kravetz wrote:
>On 9/25/19 5:18 AM, Wei Yang wrote:
>> The warning here is to make sure address(dst_addr) and length(len -
>> copied) are huge page size aligned.
>>
>> While this is ensured by:
>>
>> dst_start and len is huge page size aligned
>> dst_addr equals to dst_start and increase huge page size each time
>> copied increase huge page size each time
>
>Can we also remove the following for the same reasons?
>
>diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
>index 640ff2bd9a69..f82d5ec698d8 100644
>--- a/mm/userfaultfd.c
>+++ b/mm/userfaultfd.c
>@@ -262,7 +262,6 @@ static __always_inline ssize_t __mcopy_atomic_hugetlb(struct mm_struct *dst_mm,
> pte_t dst_pteval;
>
> BUG_ON(dst_addr >= dst_start + len);
>- VM_BUG_ON(dst_addr & ~huge_page_mask(h));
>
Thanks for your comment.
It looks good, while I lack some knowledge between vma_hpagesize and
huge_page_mask().
If they are the same, why not use the same interface for all those checks in
this function?
> /*
> * Serialize via hugetlb_fault_mutex
>
>--
>Mike Kravetz
>
>>
>> This means this warning will never be triggered.
>>
>> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
>> ---
>> mm/userfaultfd.c | 4 ----
>> 1 file changed, 4 deletions(-)
>>
>> diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
>> index c7ae74ce5ff3..7895c715000e 100644
>> --- a/mm/userfaultfd.c
>> +++ b/mm/userfaultfd.c
>> @@ -243,10 +243,6 @@ static __always_inline ssize_t __mcopy_atomic_hugetlb(struct mm_struct *dst_mm,
>> vm_shared = dst_vma->vm_flags & VM_SHARED;
>> }
>>
>> - if (WARN_ON(dst_addr & (vma_hpagesize - 1) ||
>> - (len - copied) & (vma_hpagesize - 1)))
>> - goto out_unlock;
>> -
>> /*
>> * If not shared, ensure the dst_vma has a anon_vma.
>> */
>>
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2019-09-26 0:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 12:18 Wei Yang
2019-09-25 12:18 ` [PATCH 2/2] userfaultfd: wrap the common dst_vma check into an inlined function Wei Yang
2019-09-25 17:44 ` [PATCH 1/2] userfaultfd: remove one unnecessary warn_on in __mcopy_atomic_hugetlb Mike Kravetz
2019-09-26 0:35 ` Wei Yang [this message]
2019-09-26 2:10 ` Mike Kravetz
2019-09-26 2:56 ` Wei Yang
2019-09-26 17:20 ` Mike Kravetz
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=20190926003528.GA3162@richard \
--to=richardw.yang@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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