From: Andrew Morton <akpm@linux-foundation.org>
To: linmiaohe <linmiaohe@huawei.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: mmap: Merge vma after call_mmap() if possible
Date: Thu, 16 Jul 2020 15:24:38 -0700 [thread overview]
Message-ID: <20200716152438.9317f4f95b92de75f88ea99f@linux-foundation.org> (raw)
In-Reply-To: <1594696064-1409-1-git-send-email-linmiaohe@huawei.com>
On Tue, 14 Jul 2020 11:07:44 +0800 linmiaohe <linmiaohe@huawei.com> wrote:
> From: Miaohe Lin <linmiaohe@huawei.com>
>
> The vm_flags may be changed after call_mmap() because drivers may set some
> flags for their own purpose. As a result, we failed to merge the adjacent
> vma due to the different vm_flags as userspace can't pass in the same one.
> Try to merge vma after call_mmap() to fix this issue.
>
> Signed-off-by: Hongxiang Lou <louhongxiang@huawei.com>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/mmap.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 59a4682ebf3f..9568117471f8 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -1689,7 +1689,7 @@ unsigned long mmap_region(struct file *file, unsigned long addr,
> struct list_head *uf)
> {
> struct mm_struct *mm = current->mm;
> - struct vm_area_struct *vma, *prev;
> + struct vm_area_struct *vma, *prev, *merge;
> int error;
> struct rb_node **rb_link, *rb_parent;
> unsigned long charged = 0;
> @@ -1773,6 +1773,20 @@ unsigned long mmap_region(struct file *file, unsigned long addr,
> if (error)
> goto unmap_and_free_vma;
>
> + /* If vm_flags changed after call_mmap(), we should try merge vma again
> + * as we may succeed this time.
> + */
> + if (unlikely(vm_flags != vma->vm_flags && prev)) {
> + merge = vma_merge(mm, prev, vma->vm_start, vma->vm_end, vma->vm_flags,
> + NULL, vma->vm_file, vma->vm_pgoff, NULL, NULL_VM_UFFD_CTX);
> + if (merge) {
> + fput(file);
> + vm_area_free(vma);
> + vma = merge;
> + goto unmap_writable;
Shouldn't we update local variable `vm_flags' here, to pick up the
change? And possibly `addr'?
> + }
> + }
> +
> /* Can addr have changed??
> *
> * Answer: Yes, several device drivers can do it in their
> @@ -1795,6 +1809,7 @@ unsigned long mmap_region(struct file *file, unsigned long addr,
> vma_link(mm, vma, prev, rb_link, rb_parent);
> /* Once vma denies write, undo our temporary denial count */
> if (file) {
> +unmap_writable:
> if (vm_flags & VM_SHARED)
> mapping_unmap_writable(file->f_mapping);
> if (vm_flags & VM_DENYWRITE)
next prev parent reply other threads:[~2020-07-16 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 3:07 [PATCH] mm: mmap: Merge vma after call_mmap() if possible linmiaohe
2020-07-14 3:20 ` Andrew Morton
2020-07-16 22:24 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-14 3:55 linmiaohe
2020-07-16 7:33 linmiaohe
2020-07-17 1:04 linmiaohe
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=20200716152438.9317f4f95b92de75f88ea99f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.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;
as well as URLs for NNTP newsgroup(s).