mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: David Hildenbrand <david@redhat.com>, <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/mremap: avoid unneeded do_munmap call
Date: Sat, 2 Apr 2022 09:52:27 +0800	[thread overview]
Message-ID: <18cb65e5-e124-57be-31ed-9ea227c869df@huawei.com> (raw)
In-Reply-To: <3059b709-7d9a-079d-f7c4-f7cda6b7351e@redhat.com>

On 2022/4/1 18:38, David Hildenbrand wrote:
> On 01.04.22 10:10, Miaohe Lin wrote:
>> When old_len == new_len, do_munmap will return -EINVAL due to len == 0.
>> This errno will be simply ignored because of old_len != new_len check.
>> So it is unnecessary to call do_munmap when old_len == new_len because
>> nothing is actually done.
>>
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>>  mm/mremap.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/mremap.c b/mm/mremap.c
>> index e776d4c2345c..dd966621a056 100644
>> --- a/mm/mremap.c
>> +++ b/mm/mremap.c
>> @@ -817,9 +817,9 @@ static unsigned long mremap_to(unsigned long addr, unsigned long old_len,
>>  			goto out;
>>  	}
>>  
>> -	if (old_len >= new_len) {
>> +	if (old_len > new_len) {
>>  		ret = do_munmap(mm, addr+new_len, old_len - new_len, uf_unmap);
>> -		if (ret && old_len != new_len)
>> +		if (ret)
>>  			goto out;
>>  		old_len = new_len;
>>  	}
> 
> I remember stumbling over that myself a year ago or so but dig not
> deeper. But indeed, both variants (mmu, nommu) return -EINVAL in case
> len (old_len - new_len) == 0.
> 
> Maybe that used to be different before ecc1a8993751 ("do_mremap()
> untangling, part 2"), but it doesn't look like it.

It could be really hard to trace back to the reason. But it's clear that
this change does the same thing now and simplifies the code a bit.

> 
> Acked-by: David Hildenbrand <david@redhat.com>

Many thanks for your comment and Acked-by tag! Have a nice weekend! :)

> 


      reply	other threads:[~2022-04-02  1:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  8:10 Miaohe Lin
2022-04-01 10:38 ` David Hildenbrand
2022-04-02  1:52   ` Miaohe Lin [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=18cb65e5-e124-57be-31ed-9ea227c869df@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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®