From: Miaohe Lin <linmiaohe@huawei.com>
To: Mike Kravetz <mike.kravetz@oracle.com>, <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH 4/5] mm/hugetlb: simplify the code when alloc_huge_page() failed in hugetlb_no_page()
Date: Sat, 13 Mar 2021 10:54:08 +0800 [thread overview]
Message-ID: <1d72e0c4-de4d-351c-2867-10981f44b7fb@huawei.com> (raw)
In-Reply-To: <987f50e0-5511-7f53-c4b9-d8878d840bb5@oracle.com>
On 2021/3/13 3:58, Mike Kravetz wrote:
> On 3/8/21 3:28 AM, Miaohe Lin wrote:
>> Rework the error handling code when alloc_huge_page() failed to remove some
>> duplicated code and simplify the code slightly.
>>
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>> mm/hugetlb.c | 9 +++------
>> 1 file changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
>> index 695603071f2c..69b8de866a24 100644
>> --- a/mm/hugetlb.c
>> +++ b/mm/hugetlb.c
>> @@ -4337,13 +4337,10 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm,
>> * sure there really is no pte entry.
>> */
>> ptl = huge_pte_lock(h, mm, ptep);
>> - if (!huge_pte_none(huge_ptep_get(ptep))) {
>> - ret = 0;
>> - spin_unlock(ptl);
>> - goto out;
>> - }
>> + ret = 0;
>> + if (huge_pte_none(huge_ptep_get(ptep)))
>> + ret = vmf_error(PTR_ERR(page));
>
> This new code is simpler.
>
> The !huge_pte_none() catches an unlikely race. IMO, the existing code
> made that very clear. Would have been even more clear with an unlikely
> modifier. In any case, the lengthy comment above this code makes it
> clear why the check is there. Code changes are fine.
>
Yep, the lengthy comment above this code makes it much clear why we need the check.
Thanks for carefully review! :)
> Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
>
next prev parent reply other threads:[~2021-03-13 2:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 11:28 [PATCH 0/5] Some cleanups for hugetlb Miaohe Lin
2021-03-08 11:28 ` [PATCH 1/5] mm/hugetlb: use some helper functions to cleanup code Miaohe Lin
2021-03-08 11:28 ` [PATCH 2/5] mm/hugetlb: optimize the surplus state transfer code in move_hugetlb_state() Miaohe Lin
2021-03-08 11:28 ` [PATCH 3/5] hugetlb_cgroup: remove unnecessary VM_BUG_ON_PAGE in hugetlb_cgroup_migrate() Miaohe Lin
2021-03-12 19:46 ` Mike Kravetz
2021-03-08 11:28 ` [PATCH 4/5] mm/hugetlb: simplify the code when alloc_huge_page() failed in hugetlb_no_page() Miaohe Lin
2021-03-12 19:58 ` Mike Kravetz
2021-03-13 2:54 ` Miaohe Lin [this message]
2021-03-08 11:28 ` [PATCH 5/5] mm/hugetlb: avoid calculating fault_mutex_hash in truncate_op case Miaohe Lin
2021-03-12 20:03 ` Mike Kravetz
2021-03-13 2:49 ` Miaohe Lin
2021-03-13 21:17 ` Mike Kravetz
2021-03-15 1:50 ` Miaohe Lin
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=1d72e0c4-de4d-351c-2867-10981f44b7fb@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®